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(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)