yp(8) [netbsd man page]

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

NAME

     nis, yp -- description of the NIS (formerly YP) subsystem

SYNOPSIS

     ypbind [-ypset]
     ypbind [-ypsetme]

     ypset [-h host] [-d domain] server

     yppoll [-h host] [-d domain] mapname

     ypcat [-kt] [-d domainname] mapname
     ypcat -x

     ypmatch [-kt] [-d domainname] key ... mapname
     ypmatch -x

     ypwhich [-d domain] [[-t] -m [mname] | host]
     ypwhich -x

     ypserv [-d] [-x]

     yppush [-d domainname] [-h hostname] [-v] mapname

     ypxfr [-bcf] [-d domain] [-h host] [-s domain] [-C tid prog ipadd port] mapname

     ypinit -m [domainname]
     ypinit -s master_server [domainname]

     yptest

     rpc.yppasswdd [-noshell] [-nogecos] [-nopw] [-m arg1 arg2 ...]

DESCRIPTION

     The NIS subsystem allows network management of passwd and group file entries through the functions getpwent(3) and getgrent(3).  NIS also
     provides hooks for other client programs, such as amd(8) and rpc.bootparamd(8), that can use NIS maps.

     Password maps in standard YP are insecure, because the pw_passwd field is accessible by any user. A common solution to this is to generate a
     secure map (using ``makedbm -s'') which can only be accessed by a client bound to a privileged port.  To activate the secure map, see the
     appropriate comment in /var/yp/Makefile.yp.

     The NIS subsystem is conditionally started in /etc/rc.  See the /etc/rc.conf file for configuration variables.

SEE ALSO

     domainname(1), ypcat(1), ypmatch(1), ypwhich(1), ypclnt(3), group(5), hosts_access(5), nsswitch.conf(5), passwd(5), rc.conf(5), rc(8),
     ypbind(8), ypinit(8), yppoll(8), yppush(8), ypserv(8), ypset(8), yptest(8), ypxfr(8)

HISTORY

     The NIS client subsystem was originally written by Theo de Raadt to be compatible with Sun's implementation.  The NIS server suite was origi-
     nally written by Mats O Jansson.

BUGS

     If ypbind(8) cannot find a server, the system behaves the same way as Sun's code: it hangs.

     The 'secure map' feature is not compatible with non-BSD implementations as found e.g. in Solaris.

BSD
								 February 26, 2005							       BSD

ypset(8)						      System Manager's Manual							  ypset(8)

NAME

       ypset - point ypbind at a particular server

SYNOPSIS

       /usr/sbin/ypset [-V1  | -V2] [-d domain] [-h host] server

OPTIONS

       Bind server for the (old) v.1 NIS protocol.  Bind server for the (current) v.2 NIS protocol.

	      If  no  version  is  supplied, ypset, first attempts to set the domain for the (current) v.2 protocol. If this attempt fails, ypset,
	      then attempts to set the domain for the (old) v.1 protocol.  Set ypbind's binding on host, instead of locally. The host can be spec-
	      ified as a name or as an address.  Use domain, instead of the default domain.

DESCRIPTION

       The  ypset  command  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.

									  Note

       The ypbind process will refuse ypset requests unless -ypset or -ypsetme are specified when ypbind is started.

       The ypset command 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.

       The server indicates the NIS server to bind to, and can be specified as a name or an address.  If specified as a name, ypset  will  attempt
       to use NIS services to resolve the name to an address.  This will work only if the node has a current valid binding for the domain in ques-
       tion. In most cases, server should be specified as an address.

       Refer to ypfiles(4) and ypserv(8) for an overview of NIS.

SEE ALSO

       Commands: ypwhich(1), ypserv(8)

       Files: ypfiles(4)

																	  ypset(8)