NAME [Toc] [Back]
ypinit - build and install Network Information Service databases
SYNOPSIS [Toc] [Back]
/usr/sbin/ypinit -m [DOM=NIS_domain]
/usr/sbin/ypinit -s NIS_server_name [DOM=NIS_domain]
Remarks [Toc] [Back]
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 [Toc] [Back]
ypinit is a shell script that creates Network Information Service
(NIS) databases on either a master or slave NIS server. ypinit asks a
few self-explanatory questions, and reports success or failure to the
terminal. For an overview of Network Information Service, see
ypfiles(4) and ypserv(1M).
Options [Toc] [Back]
ypinit recognizes the following options and command-line arguments:
-m Create the local host as the master server to
all maps (databases) provided in the NIS
domain (see domainname(1)). All maps are
built from scratch, either from information
provided to ypinit at run-time, or from ASCII
files in /etc. All such files should be
complete and unabbreviated, unlike how they
may exist on a NIS client machine (see
passwd(4) for examples of abbreviated files).
See ypmake(1M) for more information on how
NIS databases are built on the master server.
Note that ypinit uses the NOPUSH=1 option
when invoking make, so newly formed maps are
not immediately copied to slave servers (see
-s Create NIS databases on a slave server by
copying the databases from an existing NIS
server that serves the NIS domain.
The NIS_server_name argument should be the
host name of either the master server for all
the maps or a server on which the maps are
current and stable.
Hewlett-Packard Company - 1 - HP-UX 11i Version 2: August 2003
-c Configures the local host as a NIS client, so
that the NIS client will attempt to bind to a
particular NIS server. Invocation of ypinit
with a -c option prompts the user to
construct a list of NIS servers, in the order
of preference, to which the client will try
to bind. This list of NIS servers is stored
in the file
order for ypbind to use this list of NIS
servers, ypbind should not be invoked with -
broadcast option. (see ypbind(1M) in
ypserv(1M)). If it is so desired that it is
not necessary for a NIS client to bind to a
NIS server in a particular list, the ypinit
-c installation mechanism could be ignored.
DOM=NIS_domain Causes ypinit to construct maps for the
specified NISdomain. DOM defaults to the NIS
domain shown by the domainname command (see
DIAGNOSTICS [Toc] [Back]
ypinit returns exit code 0 if no errors occur; otherwise, it returns
exit code 1.
AUTHOR [Toc] [Back]
ypinit was developed by Sun Microsystems, Inc.
FILES [Toc] [Back]
SEE ALSO [Toc] [Back]
domainname(1), makedbm(1M), ypmake(1M), yppush(1M), ypserv(1M),
ypxfr(1M), ypxfrd(1M), group(4), hosts(4), netgroup(4), networks(4),
passwd(4), protocols(4), publickey(4), rpc(4), services(4),
Hewlett-Packard Company - 2 - HP-UX 11i Version 2: August 2003 [ Back ]