ypset(1M) ypset(1M)NAME ypset - sets ypbind to a particular domain and Network Information Service (NIS) server SYNOPSIS ypset [-V1] [-d domain-name] [-h host-name] server ypset [-V2] [-d domain-name] [-h host-name] server ARGUMENTS -d domain-name Causes ypset to set ypbind to the domain specified by domain-name rather than to the local system's domain. -h host-name Causes ypset to set ypbind on the host specified by host-name instead of the local system. The value of host-name can be a host name or an Internet address. server Specifies the NIS server with which to bind. The value of server can be the host name of the server or its Internet address. If specified as a host name, ypset attempts to use NIS services to resolve the name to an Internet address. This scheme works only if the system has a current valid binding for the domain in question. Therefore, in most cases, server is specified as an Internet address. -V1 Binds for the version 1 NIS protocol. This is an old version. -V2 Binds for the version 2 NIS protocol. This is the current version. If you do not use this option, ypset first attempts to set the domain for the version 2 protocol. If this attempt fails, ypset attempts to set the domain for the version 1 protocol. DESCRIPTION ypset tells ypbind to get NIS services for a domain from the ypserv process running on a specific server. The ypset command is useful for binding a client system that is not on a broadcast network, or for binding a client system that is on a broadcast network that doesn't have an NIS server. In addition, ypset is useful for debugging NIS client applications, for example in the case of an NIS map that is available on just one NIS server. If a binding is set and the specified server later becomes unavailable, the unavailability is not discovered until an NIS client process tries to get a binding for the domain. January 1992 1
ypset(1M) ypset(1M)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. When several systems on the local network supply NIS services, ypbind can rebind to another system even while you attempt to find out if the previous ypset operation succeeded. Consider this sequence: ypset host1 ypwhich The output of the ypwhich command may not be host1. Such a result is a function of the NIS subsystem's attempt to balance the load among the available NIS servers. This situation occurs when host1 does not respond to ypbind, because it is not running ypserv or is overloaded, and another server gets the binding. Refer to ypfiles(4) and ypserv(1M) for an overview of NIS. STATUS ERROR MESSAGES AND VALUES If you are trying to change the binding of the local ypbind process and it was not started with the -ypset or -ypsetme option, ypset displays this error message: Sorry, I couldn't send my rpc message to ypbind on host host-name The same error message is displayed if you are trying to change the binding of a remote ypbind process that was not started with the ypset option or if you are trying to change the binding of a remote ypbind process that was started with the ypsetme option. FILES /etc/yp/ypset Executable file SEE ALSO ypserv(1M) ypwhich(1) in A/UX Command Reference ypfiles(4) in A/UX Programmer's Reference Chapter 4, ``Setting Up the Network Information Service,'' in A/UX Network System Administration 2 January 1992