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

________________________________________________________________

___ ___

ypset(1M) ypset(1M)

NAME

ypset - bind to particular Network Information Service server

SYNOPSIS

/usr/sbin/ypset [-V1][-h host ][-d domain ] server

Remarks

The Network Information Service (NIS) was formerly known as Yellow Pages (yp). Although the name has

changed, the functionality of the service remains the same.

DESCRIPTION

ypset tells ypbind to get Network Information Service (NIS) services for the speciﬁed domain from the

ypserv process running on server (see ypserv(1M) and ypbind(1M)). server is the NIS server that the NIS

client binds to, and is speciﬁed as either a host name or an IP address. If server is down or is not running

ypserv, this is not discovered until a local NIS client process tries to obtain a binding for the domain. The

ypbind daemon then tests the binding set by ypset. If the binding cannot be made to the requested

server, ypbind attempts to rebind to another server in the same domain.

The ypset command is useful for binding a client node that is not on a broadcast network, since broad-

casting is the method by which ypbind locates a

NIS server. If a client node exists on a broadcast net-

work which has no

NIS server running, and if there is a network with one running that is available via a

gateway, ypset can establish a binding through that gateway. It is also useful for debugging NIS client

applicationssuch as when a

NIS map exists only at a single NIS server.

In cases where several hosts on the local net are supplying NIS services, it is possible for ypbind

rebind to another host, even while you attempt to ﬁnd out if the

ypset operation succeeded. For exam-

ple, typing

ypset host1 followed by ypwhich and receiving the reply host2 may be confusing. It

could occur when host1 does not respond to ypbind because its ypserv process is not running or is

overloaded, and host2, running ypserv, gets the binding.

Refer to ypﬁles(4) and ypserv(1M) for an overview of the Network Information Service.

Options

ypset recognizes the following options and command-line arguments:

-V1 Bind server for the (old) Version 1 NIS protocol.

-h host Set the binding on host instead of locally. host can be speciﬁed as a host name or an

IP address.

-d domain Use domain instead of the default domain returned by domainname (see domain-

name(1)).

DIAGNOTICS

Sorry, ypbind on host ’name’ has rejected your request.

The user is not root, or ypbind was run without the -ypset ﬂags. See ypserv(1M) for explanations

of the -ypset ﬂags.

Sorry, I couldn’t send my rpc message to ypbind on host ’name’.

The user is not root, or ypbind was run without one of the -ypset ﬂags. See ypserv(1M) for expla-

nations of the

-ypset ﬂags.

WARNINGS

The server is the NIS server to bind to, speciﬁed as either a host name or an IP address. If server is a host

name,

ypset uses the NIS services’ hosts database (built from

/etc/hosts on the master server) to

resolve the name to an IP address. This process works only if the node currently has a valid binding for the

domain in question. In most cases, server should be speciﬁed as an

IP address.

AUTHOR

ypset was developed by Sun Microsystems, Inc.