ypmatch(1) User Commands ypmatch(1)NAME
ypmatch - print the value of one or more keys from a NIS map
SYNOPSIS
ypmatch [-k] [-t] [-d domain] key [key...] mname
ypmatch -x
DESCRIPTION
ypmatch prints the values associated with one or more keys from the NIS's name services map specified by mname, which may be either a map
name or a map nickname.
Multiple keys can be specified; all keys will be searched for in the same map. The keys must be the same case and length. No pattern match-
ing is available. If a key is not matched, a diagnostic message is produced.
OPTIONS
The following options are supported:
-k Before printing the value of a key, print the key itself, followed by a colon (:).
-t Inhibit map nickname translation.
-d domain Specify a domain other than the default domain.
-x Display the map nickname table. This lists the nicknames the command knows of, and indicates the map name associated with
each nickname.
OPERANDS
The following operand is supported:
mname The NIS's name services map
EXIT STATUS
The following exit values are returned:
0 Successful operation.
1 An error occurred.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWnisu |
+-----------------------------+-----------------------------+
SEE ALSO ypcat(1), ypfiles(4), attributes(5)NOTES
ypmatch will fail with an RPC error message on yp operation if enough file descriptors are not available. The number of file descriptors
should be increased if this occurs.
SunOS 5.10 22 Aug 1997 ypmatch(1)
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