ypbind(8) [osx man page]

YPBIND(8)						    BSD System Manager's Manual 						 YPBIND(8)

NAME

     ypbind -- create and maintain a binding to a YP server

SYNOPSIS

     ypbind [-ypset] [-ypsetme] [-insecure]

DESCRIPTION

     ypbind finds the server for a particular YP domain and stores information about it in a binding file. This binding information includes the
     IP address of the server associated with that particular domain and which port the server is using.  This information is stored in the direc-
     tory /var/yp/binding in a file named with the convention DOMAINNAME.version. (The YP system only supplies information on version 2.)

     When ypbind starts the primary domain (or gets the first request for a new domain), it checks if a file for the domain in question exists in
     the directory /var/yp/binding (ie. /var/yp/binding/DOMAINNAME.ypservers).	If such a file exists, it will list the hosts which ypbind should
     restrict its server search to.  Otherwise, ypbind assumes it will need to use broadcasts to find a valid server.  Using either of these tech-
     niques, ypbind will search for a server willing to serve maps for the client's domain.  Once a binding is established, ypbind maintains this
     binding by periodically communicating with the server to which it is bound.  If the binding is somehow lost, e.g by server reboot, ypbind
     marks the domain as unbound and attempts to re-establish the binding.  When the binding is once again successful, ypbind marks the domain as
     bound and resumes its periodic check.

     The options are as follows:

     -ypset    ypset(8) may be used to change the server to which a domain is bound.

     -ypsetme  ypset(8) may be used only from this machine to change the server to which a domain is bound.

     -insecure
	       permit binding to a ypserv(8) on a non-reserved port.  This is needed if receiving maps from SunOS 3.x or Ultrix.

     -d        enable debugging output.

     The -ypset and -ypsetme options are dangerous and should be avoided.  For greatest security, the use of a server list in
     /var/yp/binding/DOMAINNAME.ypservers is recommended.  The file should contain a list of valid YP server hostnames, with one hostname per
     line.  The comment character is #.

FILES

     /var/yp/binding/DOMAINNAME.version - binding file for domainname /var/yp/binding/DOMAINNAME.ypservers - server list for this particular
     domain

SEE ALSO

     domainname(1), ypcat(1), ypmatch(1), yppoll(8), ypset(8), ypwhich(1), ypserv(8), yp(8)

AUTHOR

     Theo de Raadt

BSD
								 October 25, 1994							       BSD

ypset(1M)						  System Administration Commands						 ypset(1M)

NAME

       ypset - point ypbind at a particular server

SYNOPSIS

       /usr/sbin/ypset [-d ypdomain] [-h host] server

DESCRIPTION

       In order to run ypset, ypbind must be initiated with the -ypset or -ypsetme options. See ypbind(1M). ypset tells ypbind to get NIS services
       for the specified ypdomain from the ypserv process running on server. If server is down, or is not running ypserv, this might not  be  dis-
       covered	until an NIS client process tries to obtain a binding for the domain. At this point, the binding set by ypset is tested by ypbind.
       If the binding is invalid, ypbind attempts to rebind for the same domain.

       ypset is useful for binding a client node that is not on a broadcast net, or is on a broadcast net that is not running an NIS server  host.
       It is also useful for debugging NIS client applications, for instance, where an NIS map exists only at a single NIS server host.

       Where  several  hosts on the local net are supplying NIS services, ypbind can rebind to another host, even while you attempt to find out if
       the ypset operation succeeded.  For example, if you enter the ypset command below, you might get the subsequent response from ypwhich:

       example% ypset host1
       example% ypwhich
       host2

       The sequence shown above is a function of the NIS subsystem's attempt to load-balance among the available  NIS  servers,  and  occurs  when
       host1 does not respond to ypbind because it is not running ypserv (or is overloaded), and host2, running ypserv, obtains the binding.

       server  indicates  which NIS server to bind to, and must be specified as a name or an IP address. This works only if the node has a current
       valid binding for the domain in question and ypbind has been set to allow use of ypset.	In most cases, server should be specified as an IP
       address.

       ypset  tries  to  bind over a connectionless transport.	The NIS library call, yp_all(), uses connection-oriented transport and derives the
       NIS server's address  based on the connectionless address supplied by ypset.

       Refer to ypfiles(4) for an overview of the NIS name service.

OPTIONS

       -d ypdomain     Use ypdomain, instead of the default domain.

       -h host	       Set ypbind's binding on host, instead of locally. Specify host as a name.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWnisu			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       ypwhich(1), ypfiles(4), attributes(5)

SunOS 5.10							    14 Sep 1992 							 ypset(1M)