DistributedNetworks DistributedNetworks

NIS Client Networking  «Prev 

yp functions

Note: The yp function is rarely used today within the context of Red Hat Linux. An enhanced yp-tools package that provides an enhancement is now available for Red Hat Enterprise Linux 6.
yp functions: 1) ypbind, 2) ypcat, 3) ypwhich, 4) ypmatch, 5) yppoll

Properly Configured NIS Setup

A properly configured NIS setup involves configuring at least one NIS server and one or more NIS clients. If your Red Hat Linux system is going to be part of a network with existing NIS servers, you only need to install and configure the client programs, ypbind, ypwhich, ypcat, yppoll, and ypmatch. The most important program is the NIS client daemon, ypbind. ypbind is usually started from the system's startup procedure. As soon as ypbind is running your system has become an NIS client.
On the other hand, if your Red Hat Linux system is going to be part of a network that does not already have NIS servers in place, you need to configure at least one NIS server, which involves configuring the ypserv client daemon and identifying the files that NIS distributes to client programs and, optionally, to slave servers.

ypbind daemon

After you have succesfully compiled the software you are now ready to install it. A suitable place for the ypbind[1] daemon is the directory

Some people may tell you that you do not need ypbind on a system with NYS and this is incorrect. ypwhich and ypcat require the ypbind daemon.
You must do this as root and the other binaries (ypwhich, ypcat, yppasswd, yppoll, ypmatch) should go in a directory accessible by all users, normally /usr/bin.
Newer ypbind versions have a configuration file called
You can hardcode a NIS server there. You will require this file for NYS.


[1]ypbind: Binds to an NIS (Network Information Service) master server (if NIS is configured), and starts or stops the ypbind process, which communicates with the master server.