yptest(8) System Manager's Manual yptest(8)NAME
yptest - test NIS configuration
SYNOPSIS
yptest [-q] [-d domain] [-h host] [-m map] [-u user]
DESCRIPTION
yptest calls various NIS functions to check if the NIS configuration is correct and works as expected.
OPTIONS -q Be quiet, don't print messages
-d domainname
Specify a domain other than the default domain as returned by domainname(8). This option is not supported by all tests.
-h hostname
Query ypserv on hostname instead of the currently used one. This option is not supported by all tests.
-m map Use the map map for the tests instead of passwd.byname. This option should be used if the default map does not exist.
-u user
Use the account user instead of nobody. This option should be used if the nobody account does not exist in the map used for testing
(passwd.byname or the one given with the -m option).
SEE ALSO domainname(8), ypbind(8), ypcat(8), ypmatch(1), ypserv(8), yppoll(8), ypwhich(1)AUTHOR
yptest is part of the yp-tools package, which was written by Thorsten Kukuk <kukuk@linux-nis.org>.
YP Tools 2.12 April 2010 yptest(8)
Check Out this Related 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