Administering NIS (Linux in a Nutshell, 3rd Edition)

start page | rating of books | rating of authors | reviews | copyrights

2.7. Administering NIS

NIS is enabled by setting up NIS servers and NIS clients. The descriptions given here describe NIS setup using ypserv, which does not support a master/slave server configuration. All NIS commands depend on the RPC portmap program, so make sure it is installed and running before setting up NIS.

2.7.1. Setting up an NIS server

Setting up an NIS server involves:

Setting a domain name for NIS using domainname
Editing the ypMakefile, which identifies which databases to build and what sources to use in building them
Copying the ypMakefile to /var/yp/Makefile
Running make from the /var/yp directory, which builds the databases and initializes the server
Starting ypserv, the NIS server daemon

2.7.2. Setting up an NIS client

Setting up an NIS client involves setting the domain name for NIS using domainname, which should be the same name used by the NIS server, and running ypbind.

2.7.3. NIS User Accounts

NIS networks have two kinds of user accounts: distributed and local. Distributed accounts must be administered from the master machine; they provide information that is uniform on each machine in an NIS domain. Changes made to distributed accounts are distributed via NIS maps. Local accounts are administered from the local computer; they provide account information unique to a specific machine. They are not affected by NIS maps, and changes made to local accounts do not affect NIS. When NIS is installed, preexisting accounts default to local accounts.


2.6. Overview of NIS		2.8. RPC and XDR