Configuring the Network Information Service (NIS)

Setting up an NIS server

A number of items must be verified, and perhaps modified, in preparation of enabling an NIS server:

See also:


An NIS server reads the file /etc/yp/YP_MAP_X_LATE to obtain the list of files to service. Edit the file /etc/yp/YP_MAP_X_LATE to remove names of files you do not wish NIS to service and add those you do.

The file /etc/yp/YP_MAP_X_LATE supports a facility for mapping map names that are longer than operating system length limits into alias names; the maps are then allowed to reside on the system under the alias name but still be known to NIS programs by a universal map name. You must assign an NIS alias to a map if a map name exceeds the filename length limit allowed by your operating system (often 14 characters; however, DTFS, EAFS, and HTFS filesystems have a filename limit of 255 characters). For more information on aliasing map names see ypmapxlate(NF).

Verify that the files listed in /etc/yp/YP_MAP_X_LATE are complete and current on your master server. All files listed in /etc/yp/YP_MAP_X_LATE must be available to the master server.

See also:

Checking the NIS domain name

Ensure that the NIS domain name is set to NULL by entering domainname at your prompt. If the screen returns anything other than NULL, enter domainname "". ypinit and mkdev nis do not enter the appropriate command in the NIS startup script unless your domain name is set to NULL. domainname(NC) sets or displays the name of the current NIS domain.

See also:

Adding NIS to your PATH variables

For the root account, add the following entry to the PATH variable of the /.profile file (if you are running the Bourne or Korn shell) or /.cshrc file (if you are running the C shell):


Next topic: Initializing NIS
Previous topic: Security

© 2003 Caldera International, Inc. All rights reserved.
SCO OpenServer Release 5.0.7 -- 11 February 2003