1ypbind(8) System Manager's Manual ypbind(8)
2
6 ypbind - NIS binding process
7
9 ypbind [ -c ] [ -d|-debug ] [ -v|-verbose ] [ -broadcast ] [ -broken-
10 server ] [ -ypset ] [ -ypsetme ] [ -no-ping ] [ -f configfile ] [
11 -local-only ] [ -ping-interval ping-interval ]
12 ypbind --version
14
16 ypbind finds the server for NIS domains and maintains the NIS binding
17 information. The client (normaly the NIS routines in the standard C
18 library) could get the information over RPC from ypbind or read the
19 binding files. The binding files resides in the directory /var/yp/bind‐
20 ing and are conventionally named [domainname].[version]. The supported
21 versions are 1 and 2. There could be several such files since it is
22 possible for an NIS client to be bound to more then one domain.
23 After a binding has been established, ypbind will send YPPROC_DOMAIN
25 requests to the current NIS server at 20 seconds intervals. If it
26 doesn't get an response or the NIS server reports that he doesn't have
27 this domain any longer, ypbind will search for a new NIS server. All 15
28 minutes ypbind will check to see if the current NIS server is the
29 fastest. If it find a server which answers faster, it will switch to
30 this server. You could tell ypbind to use network broadcasts to find a
31 new server, what is insecure, or you could give it a list of known
32 secure servers. In this case ypbind will send a ping to all servers
33 and binds to first one which answers.
34 Unless the option -debug is used, ypbind detaches itself from the con‐
36 trolling terminal and puts itself into background. ypbind uses sys‐
37 log(3) for logging errors and warnings. At startup or when receiving
38 signal SIGHUP, ypbind parses the file /etc/yp.conf and tries to use the
39 entries for its initial binding. Valid entries are
40 domain nisdomain server hostname
42 Use server hostname for the domain nisdomain. You could have
43 more then one entry of this type for a single domain.
44 domain nisdomain broadcast
46 Use broadcast on the local net for domain nisdomain.
47 ypserver hostname
49 Use server server for the local domain.
50 A broadcast entry in the configuration file will overwrite a
52 ypserver/server entry and a ypserver/server entry broadcast. If all
53 given server are down, ypbind will not switch to use broadcast. ypbind
54 will try at first /etc/hosts and then DNS for resolving the hosts names
55 from /etc/yp.conf. If ypbind couldn't reconfigure the search order, it
56 will use only DNS. If DNS isn't available, you could only use IP-
57 addresses in /etc/hosts. ypbind could only reconfigure the search
58 order with glibc 2.x. If the -broadcast option is specified, ypbind
59 will ignore the configuration file. If the file does not exist or if
60 there are no valid entries, ypbind exit.
61 This ypbind is a special version which uses pthreads. It will start 2
63 more threads. The master process services RPC requests asking for
64 binding info. The first thread initializes the binding and checks it
65 periodically. Upon failure, the binding is invalidated and the process
66 tries again to find a valid server. The second thread will handle all
67 the signals.
68
71 -broadcast
72 Send a broadcast to request the information needed to bind to a
73 specific NIS server. With this option, /etc/yp.conf will be
74 ignored.
75 -ypset Allow root from any remote machine to change the binding for a
77 domain via the ypset(8) command. By default, no one can change
78 the binding. This option is really insecure. If you change a
79 binding for a domain, all the current known servers for this
80 domain will be forgotten. If the new server goes down, ypbind
81 will use the old searchlist.
82 -ypsetme
84 The same as -ypset, but only root on the local machine is
85 allowed to chang the binding. Such requests are only allowd from
86 loopback.
87 -c ypbind only checks if the config file has syntax errors and
89 exits.
90 -debug starts ypbind in debug mode. ypbind will not put itself into
92 background, and error messages and debug output are written to
93 standard error.
94 -verbose
96 Causes ypbind to syslog(2) any and all changes in the server its
97 bound to.
98 -broken-server
100 lets ypbind accept answers from servers running on an illegal
101 port number. This should usually be avoided, but is required by
102 some ypserv(8) versions.
103 -no-ping
105 ypbind will not check if the binding is alive. This option is
106 for use with dialup connections to prevent ypbind from keeping
107 the connection unnessecarily open or causing autodials.
108 -f configfile
110 ypbind will use configfile and not /etc/yp.conf
111 -local-only
113 ypbind will only bind to the loopback device and is not
114 reacheable from a remote network.
115 -ping-interval ping-interval
117 The default value for ypbind to check, if a NIS server is still
118 reacheable, is 20 seconds. With this options another frequency
119 in seconds can be specified.
120 --version
122 Prints the version number
123
125 Binding to multiple domains is tested and works. Load sharing between
126 multiple servers for a single domain is not supported. ypbind will
127 always try to bind a domain to a server. If there is no valid server in
128 the list or answers to a broadcast, the domain is unbounded.
129
131 /etc/yp.conf
132 configuration file.
133 /var/yp/binding/[domainname].[version]
135 binding file containing information about each NIS domain.
136 /var/run/ypbind.pid
138 contains the process id of the currently running ypbind master
139 process.
140
142 syslog(3), domainname(1), ypdomainname(8), ypwhich(1), ypserv(8),
143 ypset(8)
144
147 ypbind-mt was written by Thorsten Kukuk <kukuk@suse.de>.
148ypbind-mt Version 1.19 October 2004 ypbind(8)