ypinit(1M) ypinit(1M)NAME ypinit - initializes Network Information Service (NIS) maps for master and slave servers SYNOPSIS ypinit -m ypinit -s server-name ARGUMENTS -m Causes ypinit to make the maps that are required for a system to be an NIS master server. -s server-name Causes ypinit to make the maps that are required for a system to be an NIS slave server. The value of server-name is the name of the existing master server for which this system will act as a slave server, or the name of a reliable slave server of the existing master server. The server specified by server-name must be reachable over the network so that ypinit can copy the maps from it. DESCRIPTION ypinit uses the following files to set up NIS maps on an NIS master in /etc/yp: /etc/ethers /etc/passwd /etc/group /etc/protocols /etc/hosts /etc/rpc /etc/netgroup /etc/services /etc/network /usr/lib/aliases These files are known collectively as the default NIS files. The relationship between the master server and the slave server is as follows: ⊕ The master server is the repository of the ``master'' copies of the default NIS files. When you are adding a user to, or removing a user from, a system on the network, you should modify the /etc/passwd file on the master server only. The same restriction is true for the other default NIS files. ⊕ The slave server helps the master server respond to NIS queries. In addition, the slave server takes over when the master server is down. If the master server goes down and there is no slave server, users will be unable to log in to their systems if their password entries are served by NIS. January 1992 1
ypinit(1M) ypinit(1M)Before running ypinit, you should edit /etc/HOSTNAME to set the domain name and you should edit the default NIS files so that they contain entries for the data you want to serve to the systems in the domain. For example, you can edit /etc/passwd so that it contains an entry for each user of a system in the domain served by this master server. Then run ypinit to make the NIS maps. When used with both the -m and -s options, ypinit asks the following question: Do you want this procedure to quit on non-fatal errors? You should enter y to prevent ypinit from generating unreliable maps. The ypinit script makes the maps in /etc/yp/domain-name, where domain-name is a name for the group of systems that are served by the master server. If you run ypinit a second time with the same domain name, it must remove the existing directory and rebuild it with the new maps. Before doing so, ypinit asks: Can we destroy the existing domain-name and its contents? When used with the -m option, ypinit prompts as follows: Please continue to add the names for the other hosts, one per line. When you are done with the list, type a <ctl D>. You can enter the host names of slave servers now, or you can add the names of slave servers later. When ypinit completes, verify that the value of the action field for the ypbind and ypserv entries in /etc/inittab is set to wait. For a master server, you may want to add an entry to /etc/inittab for the rpc.yppasswdd daemon. See yppasswdd(1M) for details. The next time you restart the system, it will come up as an NIS master or slave server. FILES /etc/ethers File associating an Ethernet address to a host name /etc/group File containing information about groups and the users who belong to them /etc/hosts File associating an Internet address with its host name /etc/netgroup 2 January 1992
ypinit(1M) ypinit(1M)File that defines network-wide groups and the users who belong to them /etc/networks File associating a network name with its network number /etc/passwd File containing information required for a user to log in /etc/protocols File associating a protocol name with a protocol number /etc/services File associating a service name with a port number, protocol name, and any aliases /etc/yp/ypinit Executable file SEE ALSO makedbm(1M), ypmake(1M), yppasswdd(1M), yppush(1M), ypserv(1M), ypxfr(1M) ypfiles(4) in A/UX Programmer's Reference Chapter 4, ``Setting Up the Network Information Service,'' in A/UX Network System Administration January 1992 3