Directed NIS setup

Stand Alone Linux machine NIS services setup.

Stand alone Linux machines (i.e. not CUE Level 1) at JLAB are required to follow the instructions below to configure NIS services.

This page outlines the steps to verify that your system is configured correctly to utilize directed NIS.

The JLAB NIS system on some Linux, Solaris and HP-UX servers and clients currently employs a broadcast binding method. This method
requires NIS servers to exist on each subnet. Directed NIS provides a way for a system to bind to server regardless of its location on the network. This approach reduces the numbers of NIS server necessary which in turn simplifies the management of the NIS system site wide. Most of the currently active NIS servers will be retired soon, meaning that if you do not perform the steps below, you may not be able to login to your system.

If you have a CUE level two or Standalone build of Linux, verify that the /etc/yp.conf file on the system has the following content:

/etc/yp.conf file

domain CCCHP server nis1
domain CCCHP server nis2
domain CCCHP server nis3
domain CCCHP server nis4

Once the configuration files are in place as indicated above you are now ready to switch your system to directed NIS mode. This is
accomplished by simply restarting you ypbind daemon (or simply reboot your machine)

From the command line as root type:
# /etc/init.d/ypbind stop
# /etc/init.d/ypbind start
# ypwhich (This should return the name of the NIS server that the system is bound to.)

NOTE: in some cases ypwhich has to be run two times before it returns the name of the NIS server

Questions ? Contact Helpdesk {helpdesk@jlab.org}

This document is maintained by {helpdesk@jlab.org}