HP-UX Reference (11i v1 00/12) - 1M System Administration Commands N-Z (vol 4)

ManualsBrandsHP ManualsSoftwareHP-UX Reference Manuals

581

582

583

584

585

586

587

588

589

590

__________________________________________________________________________________________________________________________________________________________________________________________________

STANDARD Printed by: Nora Chuang [nchuang] STANDARD

/build/1111/BRICK/man1m/naaagt.1m

________________________________________________________________

___ ___

ypserv(1M) ypserv(1M)

Client requests drive the binding process. As a request for an unbound domain comes in, the ypbind pro-

cess broadcasts on the network trying to ﬁnd a ypserv process serving maps within that NIS domain.

Since the binding is establishedby broadcasting, at least one ypserv process must exist on every network.

Once a binding is established for a client, it is given to subsequent client requests. Execute ypwhich to

query the ypbind process (local and remote) for its current binding (see ypwhich(1)).

Bindings are veriﬁed before they are given to a client process. If ypbind is unable to transact with the

ypserv process it is bound to, it marks the domain as unbound, tells the client process that the domain is

unbound, and tries to bind again. Requests received for an unbound domain fail immediately. Generally, a

bound domain is marked as unbound when the node running ypserv crashes or is overloaded. In such a

case, ypbind binds to any NIS server (typically one that is less heavily loaded) that is available on the

network.

The ypbind daemon also accepts requests to set its binding for a particular domain. ypset accesses the

Set_domain facility; it is for unsnarling messes and is not for casual use.

Options

ypserv recognizes the following options:

-l log_file Log diagnostic and error messages to the ﬁle, log_ﬁle.

ypserv is started without the -l option,

ypserv writes its messages to

/var/yp/ypserv.log

if that ﬁle exists.

ypbind is started without the -l option, ypbind writes its messages directly to

the system console, /dev/console .

Information logged to the ﬁle includes the date and time of the message, the host

name, the process id and name of the function generating the message, and the mes-

sage itself. Note that different services can share a single log ﬁle since enough infor-

mation is included to uniquely identify each message.

ypbind recognizes the following options:

-l log_file Log diagnostic and error messages to the ﬁle, log_ﬁle. See the description above.

-s Secure. When speciﬁed, only NIS servers bound to a reserved port are used. This

allows for a slight increase in security in completely controlled environments, where

there are no computers operated by untrusted individuals. It offers no real increase in

security.

-ypset Allow ypset to be used to change the binding (see ypset(1M)). For maximum secu-

rity, this option should be used only when debugging the network from a remote

machine.

-ypsetme Allow ypset to be issued from this machine (see ypset(1M)). Security is based on IP

address checking, which can be defeated on networks where untrusted individuals

may inject packets. This option is not recommended.

AUTHOR

ypserv, ypbind, and ypxfrd were developed by Sun Microsystems, Inc.

FILES

/var/yp/binding/domainname

.version

These ﬁles cache the last successful binding created for the given

domain, in order to to speed up the binding process. When a binding

is requested, these ﬁles are checked for validity and then used.

/var/yp/securenets This ﬁle is read by ypxfrd and ypserv. It contains a list of IP

addresses that these servers will allow a binding to.

/var/yp/secureservers This ﬁle is read by ypbind. It contains a list of IP addresses that

ypbind will receive a binding from.