ypinit(1m) [hpux man page]
ypinit(1M) ypinit(1M) NAME
ypinit - build and install Network Information Service databases SYNOPSIS
NIS_domain] NIS_server_name NIS_domain] 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
is a shell script that creates Network Information Service (NIS) databases on either a master or slave NIS server. 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 recognizes the following options and command-line arguments: 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 pro- vided to at run-time, or from ASCII files in 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 uses the option when invoking so newly formed maps are not immediately copied to slave servers (see ypmake(1M)). 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. Configures the local host as a NIS client, so that the NIS client will attempt to bind to a particular NIS server. Invocation of with a option prompts the user to construct a list of NIS servers, in the order of preference, to which the client will try to bind. Each of these NIS servers must be listed in the file along with its IP Address. This list of NIS servers is stored in the file This file is used by when invoked without the 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 installation mechanism could be ignored. Causes to construct maps for the specified NIS_domain. defaults to the NIS domain shown by the command (see domain- name(1). RETURN VALUE
returns exit code 0 if no errors occur; otherwise, it returns exit code 1. AUTHOR
was developed by Sun Microsystems, Inc. FILES
SEE ALSO
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), ypfiles(4). ypinit(1M)
Check Out this Related Man Page
YPINIT(8) BSD System Manager's Manual YPINIT(8) NAME
ypinit -- build and install NIS databases SYNOPSIS
ypinit -m [domainname] ypinit -s master_server [domainname] ypinit -u [domainname] DESCRIPTION
The ypinit utility is a script which sets up databases on a Network Information Service (NIS) master or slave server. On a master server, ypinit creates the /var/yp/$DOMAINNAME directory, the /var/yp/ypservers file, and calls /var/yp/Makefile to create and populate an initial set of NIS maps. The maps are created from local source files using the yp_mkdb(8) utility. The utility will prompt the user for a list of servers that support the specified domain; this list is used to populate the ypservers map. On a slave server, ypinit creates the /var/yp/$DOMAINNAME, populates it with copies of the NIS maps from the master. The maps are obtained from the master using the ypxfr(8) utility. The ypinit utility obtains the list of maps to transfer in one of two ways: if the system is configured as an NIS client and is bound to the master server, ypinit is able to use the ypwhich(1) utility to obtain a list of maps exported by the master server. If the system is not configured as a client of the NIS master, ypinit uses a hardcoded list of maps, some of which may or may not actually exist on the master. The system administrator can edit the ypinit script and modify the map list if necessary. Other- wise, individual maps can be transferred manually from the master using ypxfr(8). OPTIONS
The ypinit utility supports the following options: -m [domainname] Set up a master server. By default, ypinit sets up a server for the system default domain. The user can override this default by specifying domainname explicitly. Maps are constructed from scratch using local files as templates using the yp_mkdb(8) utility. -s master_server [domainname] Set up a slave server using master_name as the master. Maps are copied from master_server to the slave using ypxfr(8). By default, ypinit sets up a server for the system default domain. The user can override this default by specifying domainname explicitly. -u [domainname] Update the ypservers map on the master server. When a new slave server is added to a domain, its hostname must be added to the ypservers map so that yppush(8) can propagate updates on the master to all of the slaves. FILES
/etc/bootparams Bootparams source file /etc/ethers Ethers data source file /etc/group Group source file /etc/hosts Hostname/IP address source file /etc/netid RPC netid source file /etc/networks Networks source file /etc/protocols Protocols source file /etc/publickey RPC public key/secret key source file /etc/services Services data source file /etc/shells Shells source file /var/yp/master.passwd Passwd database source file /var/yp/netgroup Netgroup data source file /var/yp/ypservers Ypservers source file (generated by ypinit) SEE ALSO
mknetid(8), revnetgroup(8), yp(8), yp_mkdb(8), yppush(8), ypserv(8), ypxfr(8) HISTORY
This version of ypinit is based on the ypinit script in OpenBSD. It first appeared in FreeBSD 3.0. AUTHORS
The original script was written by Mats O Jansson <moj@stacken.kth.se>. It was modified for FreeBSD by Bill Paul <wpaul@ctr.columbia.edu>. BSD
November 10, 1997 BSD