Setting up NIS

Preparing NIS databases on the master server

Setting up the master server (see ``Setting up the master server'') converts the input text files on the master server into NIS master server maps. Before doing this, however, you need to take several precautions.

The input files may be located either in the master server's /etc directory or in some other directory. Having them in /etc may have the disadvantage that then the contents of the master server's local files will be the same as those of the maps. For example, the server's local /etc/passwd file typically should contain an entry for root (and other administrative logins), but the input file used to build the password maps typically should not contain an entry for root (and other administrative logins).

If you choose to locate the input files in some other directory, then you will have to modify the Makefile in /var/yp by changing the line that says:

   DIR=/var/yp

to say:

   DIR=your_choice

(see ``Modifying the Makefile'') and treat the server's local files as those of a client.

Check the following input files on the master server to make sure they reflect an up-to-date picture of your system.

NOTE: Some of the files in this list are not used by UnixWare. They could be accessed by other machines on the network, however.

/etc/passwd
/etc/hosts
/etc/ethers
/etc/group
/etc/networks
/etc/protocols
/etc/services
/etc/bootparams
/etc/netgroup
/etc/auto.master
/etc/auto.home

An entry for the daemon user ID must be present in the local passwd file for both master and slave server. Furthermore, that entry must precede any other entries with the same user ID, as described previously for setting up the client's /etc/passwd file.

Also, make sure that the aliases input file is complete by verifying that it contains all the mail aliases that you want to have available throughout the domain. Refer to aliases(4) for more information.