1.\" Copyright (c) 1991, 1993, 1995 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 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. Neither the name of the University nor the names of its contributors 13.\" may be used to endorse or promote products derived from this software 14.\" without specific prior written permission. 15.\" 16.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 17.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 18.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 19.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 20.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 21.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 22.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 23.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 24.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 25.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 26.\" SUCH DAMAGE. 27.\" 28.Dd April 9, 1995 29.Dt YPBIND 8 30.Os 31.Sh NAME 32.Nm ypbind 33.Nd "NIS domain binding daemon" 34.Sh SYNOPSIS 35.Nm 36.Op Fl ypset 37.Op Fl ypsetme 38.Op Fl s 39.Op Fl m 40.Oo 41.Fl S 42.Sm off 43.Ar domainname , server1 , server2 , ... 44.Sm on 45.Oc 46.Sh DESCRIPTION 47The 48.Nm 49utility is the process that maintains NIS binding information. 50At startup, 51it searches for an NIS server responsible for serving the system's 52default domain (as set by the 53.Xr domainname 1 54command) using network broadcasts. 55Once it receives a reply, 56it will store the address of the server and other 57information in a special file located in 58.Pa /var/yp/binding . 59The NIS routines in the standard C library can then use this file 60when processing NIS requests. 61There may be several such files 62since it is possible for an NIS client to be bound to more than 63one domain. 64.Pp 65After a binding has been established, 66.Nm 67will send DOMAIN_NONACK requests to the NIS server at one minute 68intervals. 69If it fails to receive a reply to one of these requests, 70.Nm 71assumes that the server is no longer running and resumes its network 72broadcasts until another binding is established. 73The 74.Nm 75utility will also log warning messages using the 76.Xr syslog 3 77facility each time it detects that a server has stopped responding, 78as well as when it has bound to a new server. 79.Pp 80The following options are available: 81.Bl -tag -width indent 82.It Fl ypset 83It is possible to force 84.Nm 85to bind to a particular NIS server host for a given domain by using the 86.Xr ypset 8 87command. 88However, 89.Nm 90refuses YPBINDPROC_SETDOM requests by default since it has no way of 91knowing exactly who is sending them. 92Using the 93.Fl ypset 94flag causes 95.Nm 96to accept YPBINDPROC_SETDOM requests from any host. 97This option should only 98be used for diagnostic purposes and only for limited periods since allowing 99arbitrary users to reset the binding of an NIS client poses a severe 100security risk. 101.It Fl ypsetme 102This is similar to the 103.Fl ypset 104flag, except that it only permits YPBINDPROC_SETDOM requests to be processed 105if they originated from the local host. 106.It Fl s 107Cause 108.Nm 109to run in secure mode: it will refuse to bind to any NIS server 110that is not running as root (i.e., that is not using privileged 111TCP ports). 112.It Fl S Xo 113.Sm off 114.Ar domainname , server1 , server2 , server3 , ... 115.Sm on 116.Xc 117Allow the system administrator to lock 118.Nm 119to a particular 120domain and group of NIS servers. 121Up to ten servers can be specified. 122There must not be any spaces between the commas in the domain/server 123specification. 124This option is used to ensure that the system binds 125only to one domain and only to one of the specified servers, which 126is useful for systems that are both NIS servers and NIS 127clients: it provides a way to restrict what machines the system can 128bind to without the need for specifying the 129.Fl ypset 130or 131.Fl ypsetme 132options, which are often considered to be security holes. 133The specified 134servers must have valid entries in the local 135.Pa /etc/hosts 136file. 137IP addresses may be specified in place of hostnames. 138If 139.Nm 140cannot make sense out of the arguments, it will ignore 141the 142.Fl S 143flag and continue running normally. 144.Pp 145Note that 146.Nm 147will consider the domainname specified with the 148.Fl S 149flag to be the system default domain. 150.It Fl m 151Cause 152.Nm 153to use a 'many-cast' rather than a broadcast for choosing a server 154from the restricted mode server list. 155In many-cast mode, 156.Nm 157will transmit directly to the YPPROC_DOMAIN_NONACK procedure of the 158servers specified in the restricted list and bind to the server that 159responds the fastest. 160This mode of operation is useful for NIS clients on remote subnets 161where no local NIS servers are available. 162The 163.Fl m 164flag can only be used in conjunction with the 165.Fl S 166flag above (if used without the 167.Fl S 168flag, it has no effect). 169.El 170.Sh NOTES 171The 172.Nm 173utility will not make continuous attempts to keep secondary domains bound. 174If a server for a secondary domain fails to respond to a ping, 175.Nm 176will broadcast for a new server only once before giving up. 177If a 178client program attempts to reference the unbound domain, 179.Nm 180will try broadcasting again. 181By contrast, 182.Nm 183will automatically maintain a binding for the default domain whether 184client programs reference it or not. 185.Sh FILES 186.Bl -tag -width /etc/rc.conf -compact 187.It Pa /var/yp/binding/[domainname].[version] 188the files used to hold binding information for each NIS domain 189.It Pa /etc/rc.conf 190system configuration file where the system default domain and 191ypbind startup options are specified 192.El 193.Sh SEE ALSO 194.Xr domainname 1 , 195.Xr syslog 3 , 196.Xr yp 8 , 197.Xr ypserv 8 , 198.Xr ypset 8 199.Sh AUTHORS 200.An Theo de Raadt Aq Mt deraadt@fsa.ca 201