Manual browser: yp(8)

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


nis, ypdescription of the NIS (formerly YP) subsystem


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]


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


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.


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


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.

February 26, 2005 NetBSD 7.0