NFS Services Administrator's Guide

Configuring and Administering NIS+
Setting Up the NIS+ Namespace
Chapter 5 215
nisls -lR
The nisls command should list the domain name, the org_dir and
groups_dir NIS+ directories, the admin group, and all the standard
tables listed in Table 5-1.
6. If the host was previously an NIS server or client, set the
NIS_MASTER_SERVER, NIS_SLAVE_SERVER, and NIS_CLIENT variables
to 0 in the /etc/rc.config.d/namesvrs file.
7. Create a cron job that runs nisping -Ca at least once a day, during
a time when the network is not busy. The following example crontab
file runs nisping -Ca once a day, at 3:00 AM. It directs standard
output and standard error from the nisping command to the file
/tmp/nisping.log.
0 3 * * * /usr/lib/nis/nisping -Ca > /tmp/nisping.log 2& >1
The nisping -Ca command causes all servers of the domain to
update their tables with the changes in the transaction log and to
clear the transaction log. If you do not issue the nisping -Ca
command regularly, your transaction log may grow too large, and you
may not have enough disk space to checkpoint it.
After you run the nisserver script, the local host is set up as the root
master server and as a client of the default domain. However, the domain
tables are still empty. The next section, “To Populate the NIS+ Tables on
the Master Server”, explains how to fill the tables with data.
For more information, see the following man pages: nisserver(1M),
domainname(1M), nisls(1), nsswitch.conf(4), crontab(1),
rpc.nisd(1M), and nis(1).