You can click this button to set up your Red Hat Linux PC as an NIS client.
Next, you should generate the NIS map database by running the /usr/lib/yp/ypinit -m At this point, we have to construct a list of the hosts which will run NIS servers. Please continue to add the names for the other hosts, one per line. You can add the server names one at a time and press Ctrl-D when you are done.
When you are done with the list, type a The current list of NIS servers looks like this: lnbp200 Is this correct? gmake: Entering directory `/var/yp/admin' Updating passwd.byname... Then, you have to verify that the list of NIS servers is correct (type y).
In addition to a master server, one or more NIS slave servers may be set up to provide the NIS maps in case the master is unavailable or down.
The NIS slave servers periodically copy the NIS maps from the master server (using the command) and are able to provide these maps to clients when the master is down.
all: passwd group hosts rpc services netid protocols mail \ # netgrp shadow publickey networks ethers bootparams printcap \ # auto.master auto.local passwd.adjunct \ # timezone locale netmasks# securenets This file defines the access rights to your NIS server # for NIS clients. A clients IP address needs to match with at # least one of those.
# # One can use the word "host" instead of a netmask of # 255.255.255.255.NIS servers and clients use Remote Procedure Call (RPC) to exchange information.Network File System (NFS), described in Chapter 19, also uses RPC.Using NIS, you can maintain a single set of configuration files for a collection of computers in an NIS server.All other computers running NIS clients can then access the files.You can have multiple NIS servers in a network, each serving a different collection of computers.