1 .\" Copyright (c) 1991, 1993, 1995
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
12 .\" 3. All advertising materials mentioning features or use of this software
13 .\" must display the following acknowledgement:
14 .\" This product includes software developed by the University of
15 .\" California, Berkeley and its contributors.
16 .\" 4. Neither the name of the University nor the names of its contributors
17 .\" may be used to endorse or promote products derived from this software
18 .\" without specific prior written permission.
20 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
39 .Nd "NIS domain binding daemon"
49 .Ar domainname , server1 , server2 , ...
54 is the process that maintains NIS binding information.
56 it searches for an NIS server responsible for serving the system's
57 default domain (as set by the
59 command) using network broadcasts.
60 Once it receives a reply,
61 it will store the address of the server and other
62 information in a special file located in
64 The NIS routines in the standard C library can then use this file
65 when processing NIS requests.
66 There may be several such files
67 since it is possible for an NIS client to be bound to more than
70 After a binding has been established,
72 will send DOMAIN_NONACK requests to the NIS server at one minute
74 If it fails to receive a reply to one of these requests,
76 assumes that the server is no longer running and resumes its network
77 broadcasts until another binding is established.
79 will also log warning messages using the
81 facility each time it detects that a server has stopped responding,
82 as well as when it has bound to a new server.
84 The following options are available:
85 .Bl -tag -width indent
87 It is possible to force
89 to bind to a particular NIS server host for a given domain by using the
94 refuses YPBINDPROC_SETDOM requests by default since it has no way of
95 knowing exactly who is sending them.
100 to accept YPBINDPROC_SETDOM requests from any host.
101 This option should only
102 be used for diagnostic purposes and only for limited periods since allowing
103 arbitrary users to reset the binding of an NIS client poses a severe
106 This is similar to the
108 flag, except that it only permits YPBINDPROC_SETDOM requests to be processed
109 if they originated from the local host.
113 to run in secure mode: it will refuse to bind to any NIS server
114 that is not running as root (i.e. that is not using privileged
118 .Ar domainname , server1 , server2 , server3 , ...
121 Allow the system administrator to lock
124 domain and group of NIS servers.
125 Up to ten servers can be specified.
126 There must not be any spaces between the commas in the domain/server
128 This option is used to insure that the system binds
129 only to one domain and only to one of the specified servers, which
130 is useful for systems that are both NIS servers and NIS
131 clients: it provides a way to restrict what machines the system can
132 bind to without the need for specifying the
136 options, which are often considered to be security holes.
138 servers must have valid entries in the local
140 file. IP addresses may be specified in place of hostnames.
143 can't make sense ouf of the arguments, it will ignore
146 flag and continue running normally.
150 will consider the domainname specified with the
152 flag to be the system default domain.
156 to use a 'many-cast' rather than a broadcast for choosing a server
157 from the restricted mode server list.
160 will transmit directly to the YPPROC_DOMAIN_NONACK procedure of the
161 servers specified in the restricted list and bind to the server that
162 responds the fastest.
163 This mode of operation is useful for NIS clients on remote subnets
164 where no local NIS servers are available.
167 flag can only be used in conjunction with the
169 flag above (if used without the
171 flag, it has no effect).
176 program will not make continuous attempts to keep secondary domains bound.
177 If a server for a secondary domain fails to respond to a ping,
179 will broadcast for a new server only once before giving up.
181 client program attempts to reference the unbound domain,
183 will try broadcasting again.
186 will automatically maintain a binding for the default domain whether
187 client programs reference it ot not.
189 .Bl -tag -width /etc/rc.conf -compact
190 .It Pa /var/yp/binding/[domainname].[version]
191 the files used to hold binding information for each NIS domain
193 system configuration file where the system default domain and
194 ypbind startup options are specified
203 .An Theo de Raadt Aq deraadt@fsa.ca