/usr/sbin/ypset [ -V1|-V2 ] [ -d domain ] [ -h host ] server
ypset tells ypbind to get Network Information Service (NIS) map information for the specified domain from the ypserv process running on server. If server is down, or isn't running ypserv, this is not 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 isn't running an NIS server host. It also is useful for debugging NIS client applications, for instance where an 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: % ypset host1 % ypwhich host2
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 can be specified as a name or an IP address. If specified as a name, ypset will attempt to use NIS services to resolve the name to an IP address. This will work only if the node has a current valid binding for the domain in question. In most cases, server should be specified as an IP address.
Refer to ypfiles(4) and ypserv(8) for an overview of NIS.
ypwhich(1), ypfiles(4), ypserv(8) delim off