ypset(1m) [hpux man page]

ypset(1M)																 ypset(1M)

NAME

       ypset - bind to particular Network Information Service server

SYNOPSIS

       host] domain] server

   Remarks
       The  Network  Information  Service  (NIS) was formerly known as Yellow Pages (YP).  Although the name has changed, the functionality of the
       service remains the same.

DESCRIPTION

       tells to get Network Information Service (NIS) services for the specified domain from the process running on  server  (see  ypserv(1M)  and
       ypbind(1M)).  server is the NIS server that the NIS client binds to, and is specified as either a host name or an IP address.  If server is
       down or is not running this is not discovered until a local NIS client process tries to obtain a binding for the domain.  The  daemon  then
       tests  the  binding  set  by If the binding cannot be made to the requested server, attempts to rebind to another server in the same domain
       present in the ypservers file.

       NOTE: In order to run must be initiated with the or options.  For more information on how to initiate see ypbind(1M).

       The command is useful for binding a client node that is not on a broadcast network.  If a client node exists on a broadcast  network  which
       has no NIS server running, and if there is a network with one running that is available via a gateway, can establish a binding through that
       gateway.  It is also useful for debugging NIS client applications such as when a NIS map exists only at a single NIS server.

       In cases where several hosts on the local net are supplying NIS services, it is possible for to rebind to  another  host,  even	while  you
       attempt	to find out if the operation succeeded.  For example, typing followed by and receiving the reply may be confusing.  It could occur
       when host1 does not respond to because its process is not running or is overloaded, and host2, running gets the binding.

       The server is the NIS server to bind to, specified as either a host name or an IP address.

       Refer to ypfiles(4) and ypserv(1M) for an overview of the Network Information Service.

   Options
       recognizes the following options and command-line arguments:

	      Bind	     server for the Version 2 NIS protocol.

	      Set the binding on
			     host instead of locally.  host can be specified as a host name or an IP address.

	      Use	     domain instead of the default domain returned by (see domainname(1)).

DIAGNOSTICS

       The user is not root, or ypbind was run without the
	      flags.  See ypserv(1M) for explanations of the flags.

       The user is not root, or ypbind was run without one of the
	      flags.  See ypserv(1M) for explanations of the flags.

WARNINGS

       Starting with ONCplus version B.11.31.02, the NIS Version 1 protocol is no longer available.

AUTHOR

       was developed by Sun Microsystems, Inc.

SEE ALSO

       domainname(1), ypwhich(1), ypserv(1M), ypfiles(4).

																	 ypset(1M)

Check Out this Related Man Page

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)

Linux and UNIX Man Pages

ypset(1m) [hpux man page]

Check Out this Related Man Page