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 may not be discovered until an NIS client process tries to get a binding for the domain. At this point, the binding set by ypset will be tested by ypbind. If the binding is invalid, ypbind will attempt to rebind for the same domain.
ypset is useful for binding a client node which is not on a broadcast net, or is on a broadcast net which is not running a NIS server host. It also is useful for debugging NIS client applications, for instance where a NIS map only exists at a single NIS server host.
In cases where several hosts on the local net are supplying NIS services, it is possible for ypbind to rebind to another host even while you attempt to find out if the ypset operation succeeded. For example, you can type:
example% ypset host1 example% ypwhich
which can be confusing. This 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, gets the binding.
server indicates the NIS server to bind to, and must be specified as a name or an IP address. This will work 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.
Created by unroff & hp-tools. © by Hans-Peter Bischof. All Rights Reserved (1997).
Last modified 21/April/97