2
.\" Copyright 1998, 1999, 2002, 2004 Thorsten Kukuk, Germany
4
.\" This file is part of ypbind-mt.
6
.\" Author: Thorsten Kukuk <kukuk@suse.de>
8
.\" ypbind-mt is free software; you can redistribute it and/or
9
.\" modify it under the terms of the GNU General Public License as
10
.\" published by the Free Software Foundation; either version 2 of the
11
.\" License, or (at your option) any later version.
13
.\" ypbind-mt is distributed in the hope that it will be useful,
14
.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
15
.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
16
.\" General Public License for more details.
18
.\" You should have received a copy of the GNU General Public
19
.\" License along with ypbind-mt; see the file COPYING. If not,
20
.\" write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330,
21
.\" Boston, MA 02111-1307, USA.
23
.TH ypbind 8 "October 2004" "ypbind-mt Version @VERSION@"
25
ypbind - NIS binding process
48
.BR \-ping-interval " ping-interval"
56
finds the server for NIS domains and maintains the NIS binding
57
information. The client (normaly the NIS routines in the standard C library)
58
could get the information over RPC from
60
or read the binding files. The binding files resides in the directory
62
and are conventionally named
63
.BR [domainname].[version] .
64
The supported versions are 1 and 2.
65
There could be several such files since it is possible for an NIS client
66
to be bound to more then one domain.
68
After a binding has been established,
70
will send YPPROC_DOMAIN requests to the current NIS server at 20 seconds
71
intervals. If it doesn't get an response or the NIS server reports that he
72
doesn't have this domain any longer,
74
will search for a new NIS server. All 15 minutes
76
will check to see if the current NIS server is the fastest. If it find
77
a server which answers faster, it will switch to this server.
80
to use network broadcasts to find a new server, what is insecure,
81
or you could give it a list of known secure servers.
84
will send a ping to all servers and binds to first one which answers.
88
is used, ypbind detaches itself from the controlling terminal and puts
89
itself into background.
93
for logging errors and warnings.
94
At startup or when receiving signal SIGHUP,
98
and tries to use the entries for its initial binding. Valid entries
110
You could have more then one entry of this type for a single domain.
117
Use broadcast on the local net for domain
126
for the local domain.
129
A broadcast entry in the configuration file will overwrite a ypserver/server
130
entry and a ypserver/server entry broadcast. If all given server are down,
134
switch to use broadcast.
140
for resolving the hosts names from
144
couldn't reconfigure the search order, it will use only
148
isn't available, you could only use IP-addresses in
151
could only reconfigure the search order with glibc 2.x.
156
will ignore the configuration file.
157
If the file does not exist or if there are no valid entries,
163
is a special version which uses
165
It will start 2 more threads. The master process services RPC requests
166
asking for binding info. The first thread initializes the binding and
167
checks it periodically. Upon failure, the binding is invalidated and
168
the process tries again to find a valid server. The second thread
169
will handle all the signals.
174
Send a broadcast to request the information needed to bind to a
175
specific NIS server. With this option,
182
from any remote machine to change the binding for a domain via the
184
command. By default, no one can change the binding. This option is really
185
insecure. If you change a binding for a domain, all the current known
186
servers for this domain will be forgotten. If the new server goes down,
188
will use the old searchlist.
195
on the local machine is allowed to chang the binding. Such requests
201
only checks if the config file has syntax errors and exits.
208
will not put itself into background, and error messages and debug
209
output are written to standard error.
214
accept answers from servers running on an illegal port number. This should
215
usually be avoided, but is required by some
221
will not check if the binding is alive. This option is for use with
222
dialup connections to prevent
224
from keeping the connection unnessecarily open or causing autodials.
226
.BR "\-f" " configfile"
235
will only bind to the loopback device and is not reacheable from
238
.BR "\-ping-interval" " ping-interval"
239
The default value for
241
to check, if a NIS server is still reacheable, is 20 seconds.
242
With this options another frequency in seconds can be specified.
245
Prints the version number
248
Binding to multiple domains is tested and works.
249
Load sharing between multiple servers for a single domain is
252
will always try to bind a domain to a server. If there is no valid
253
server in the list or answers to a broadcast, the domain is unbounded.
260
.BI /var/yp/binding/[domainname].[version]
261
binding file containing information about each NIS domain.
263
.B /var/run/ypbind.pid
264
contains the process id of the currently running
271
.BR ypdomainname (8),
278
was written by Thorsten Kukuk <kukuk@suse.de>.
added
removed
ypbind-mt-1.19/man/ypbind.8.in
