Linux Journal: Tux Knows It's Nice to Share, Part 4
Mar 04, 2001, 12:42 (0 Talkback[s])
(Other stories by Marcel Gagné)
Re-Imagining Linux Platforms to Meet the Needs of Cloud Service Providers
[ Thanks to 2more0 for this link.
"Last time around, we went through the process of setting up a
NIS server. Although it's great that we've done the job of setting
up the NIS server, it isn't much good without clients. Luckily,
clients are fairly simple, so feel free to set up lots of them. On
the client system, start by opening the file /etc/yp.conf in your
favorite editor (go ahead, I dare you). There are three possible
ways of setting up the client to look for NIS servers."
domain NISDOMAIN server HOSTNAME
# Use server HOSTNAME for the domain NISDOMAIN.
"If you choose this method, then specify the NISDOMAIN and the
HOSTNAME to which you would like the client to connect. You can
have more than one such entry. Using my example of domain.nis, my
yp.conf entry would look like this."
domain mydomain.nis server testsys.mydomain.dom
"You can also set up your client to listen for NIS servers via a
broadcast. The only catch here is the servers must be on the same
subnet. You can not listen for NIS servers outside your