ypserv(1M)

NAME | SYNOPSIS | DESCRIPTION | OPTIONS | FILES | ATTRIBUTES | SUMMARY OF TRUSTED SOLARIS CHANGES | SEE ALSO | NOTES

NAME

ypserv, ypxfrd– NIS server and binder processes

SYNOPSIS

/usr/lib/netsvc/yp/ypserv [-duv]
/usr/lib/netsvc/yp/ypxfrd

DESCRIPTION

The Network Information Service (NIS) provides a simple network lookup service consisting of databases and processes. The databases are ndbm files in a directory tree rooted at /var/yp. See dbm_clearerr(3C). These files are described in ypfiles(4). The processes are /usr/lib/netsvc/yp/ypserv, the NIS database lookup server, and /usr/lib/netsvc/yp/ypbind, the NIS binder. The programmatic interface to the NIS service is described in ypclnt(3NSL). Administrative tools are described in yppoll(1M), yppush(1M), ypset(1M), ypxfr(1M), and ypwhich(1). Tools to see the contents of NIS maps are described in ypcat(1), and ypmatch(1). Database generation and maintenance tools are described in ypinit(1M), ypmake(1M), and makedbm(1M).

The ypserv utility is a daemon process typically activated at system startup from /etc/init.d/rpc. Alternatively, it can be started on the command line using ypstart(1M) from the Trusted Path with these privileges: file_dac_read, net_downgrade_sl, net_upgrade_sl, net_mac_read, net_privaddr, proc_setclr, andproc_setsl. ypserv runs only on NIS server machines with a complete NIS database. You can halt all NIS services using the ypstop(1M) command run from the Trusted Path with the proc_owner privilege.

The ypxfrd utility transfers entire NIS maps in an efficient manner. For systems that use this daemon, map transfers are 10 to 100 times faster, depending on the map. To use this daemon, be sure ypxfrd is running on the master server. See /usr/lib/netsvc/yp/ypstart. ypxfr attempts to use ypxfrd first. If that fails, it prints a warning, then uses the older transfer method. ypxfrd must be run from the Trusted Path and inherit the net_broadcast, net_downgrade_sl, net_upgrade_sl, net_mac_read, net_privaddr, proc_setclr, and proc_setsl privileges.

The ypserv daemon's primary function is to look up information in its local database of NIS maps.

The operations performed by ypserv are defined for the implementor by the YP Protocol Specification, and for the programmer by the header file <rpcsvc/yp_prot.h>.

Communication to and from ypserv is by means of RPC calls. Lookup functions are described in ypclnt(3NSL), and are supplied as C-callable functions in the libnsl(3LIB) library. There are four lookup functions, all of which are performed on a specified map within some NIS domain: yp_match(3NSL), yp_first(3NSL), yp_next(3NSL), and yp_all(3NSL). The yp_match operation takes a key, and returns the associated value. The yp_first operation returns the first key-value pair from the map, and yp_next can be used to enumerate the remainder. yp_all ships the entire map to the requester as the response to a single RPC request.

A number of special keys in the DBM files can alter the way in which ypserv operates. The keys of interest are:

YP_INTERDOMAIN

The presence of this key causes ypserv to forward to a DNS server host lookups that cannot be satisfied by the DBM files.

YP_SECURE

This key causes ypserv to answer only questions coming from clients on reserved ports.

YP_MULTI_hostname

This is a special key in the form, YP_MULTI_hostname addr1,...,addrN. A client looking for hostname receives the “closest“ address.

Two other functions supply information about the map, rather than map entries: yp_order(3NSL), and yp_master(3NSL). In fact, both order number and master name exist in the map as key-value pairs, but the server will not return either through the normal lookup functions. If you examine the map with makedbm(1M), however, they are visible. Other functions are used within the NIS service subsystem itself, and are not of general interest to NIS clients. They include do_you_serve_this_domain?, transfer_map, and reinitialize_internal_state.

OPTIONS

ypserv

-d

The NIS service should go to the DNS for more host information. This requires the existence of a correct /etc/resolv.conf file pointing at a machine running in.named(1M). This option turns on DNS forwarding regardless of whether or not the YP_INTERDOMAIN flag is set in the hosts maps. See makedbm(1M). In the absence of an /etc/resolv.conf file, ypserv complains, but ignores the -d option.

-u

Allow non-Trusted Solaris TCB machines to be clients.

-v

Operate in the verbose mode, printing diagnostic messages to stderr.

FILES

/var/yp/securenets

Defines the hosts and networks that are granted access to information in the served domain; it is read at startup time by both ypserv and ypxfrd.

/etc/init.d/rpc

Startup file that starts up basic RPC services and NIS by calling ypstart(1M). If the /var/yp/ypserv.log file exists when ypserv starts up, log information is written to it when error conditions arise. The file /var/yp/binding/domainname/ypservers is used to list the NIS server hosts that ypbind can bind to.

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE	ATTRIBUTE VALUE
Availability	SUNWypu

SUMMARY OF TRUSTED SOLARIS CHANGES

ypserv can be started on the command line using ypstart(1M) from the Trusted Path with these privileges: file_dac_read, net_downgrade_sl, net_upgrade_sl, net_mac_read, net_privaddr, proc_setclr, andproc_setsl. The ypstop(1M) command must run from the Trusted Path with the proc_owner privilege

Upon startup, ypxfrd must inherit the net_broadcast, net_downgrade_sl, net_upgrade_sl, net_mac_read, net_privaddr, proc_setclr, and proc_setsl privileges.

-u allows non-Trusted Solaris TCB machines to be clients.

SEE ALSO

Trusted Solaris 8 HW 12/02 Reference Manual

in.named(1M), ypbind(1M), ypxfr(1M)

SunOS 5.8 Reference Manual

ypcat(1), ypmatch(1), ypwhich(1), domainname(1M), makedbm(1M), ypinit(1M), ypmake(1M), yppoll(1M), yppush(1M), ypset(1M), ypstart(1M), ypstop(1M), dbm_clearerr(3C), ypclnt(3NSL), libnsl(3LIB), securenets(4), ypfiles(4), attributes(5)

Network Interfaces Programmer's Guide

System Administration Guide, Volume 1

NOTES

ypserv supports multiple domains. The ypserv process determines the domains it serves by looking for directories of the same name in the directory /var/yp. It replies to all broadcasts requesting yp service for that domain.

The Network Information Service (NIS) was formerly known as Sun Yellow Pages (YP). The functionality of the two remains the same; only the name has changed. The name Yellow Pages is a registered trademark in the United Kingdom of British Telecommunications PLC, and must not be used without permission.

Trusted Solaris 8 HW 12/02  Last Revised 28 Jul 2000

NAME | SYNOPSIS | DESCRIPTION | OPTIONS | FILES | ATTRIBUTES | SUMMARY OF TRUSTED SOLARIS CHANGES | SEE ALSO | NOTES