Network Information Service (NIS) B.11.31.04 Administrator's Guide

# ypinit -c

The system displays the following information:

If it is desired that NIS client, has to bind to a

particular NIS server, a list of NIS servers should be constructed.

Please continue to add the names of NIS servers in the order of

preference, one per line. When done with the list, type a Ctrl+D

or a return on a line by itself

next host to add: <host name>

next host to add:

The current list of yp servers looks like this:

Is this correct? [y/n: y]

8. Start the NIS client processes:

# /sbin/init.d/nis.client start

For more information, see domainname (1), ypbind (1M), and nsswitch.conf (4). For

information about how to make the client bind to a particular server, see “Binding an

NIS Client to a Server on a Different Subnet” (page 57).

Verifying the NIS Client Configuration

To verify the NIS client configuration, complete the following steps:

1. Log in to the NIS client as a superuser.

2. List the NIS maps and the master server that serves the maps:

# /usr/bin/ypwhich -m

The ypwhich -m command lists all the NIS maps available to the client, and displays

the name of the master server that serves each map.

An output similar to the following is displayed:

auto.master mastername

netid.byname mastername

publickey.byname mastername

mail.byaddr mastername

mail.aliases mastername

netgroup.byhost mastername

netgroup.byuser mastername

netgroup mastername

protocols.byname mastername

protocols.bynumber mastername

servi.bynp mastername

services.byname mastername

rpc.byname mastername

rpc.bynumber mastername

networks.byaddr mastername

54 Configuring and Administering an NIS Client