I am running NIS on a group of machines and I have a couple of questions.
Everything seems to run alright (apart from the yppasswd command being
very lax and having extremely crappy error messages) until I configure
a slave server.
During nissetup I am informed that an NIS server must specify itself first.
Why? I don't know.
Now the slave server wants to get its passwd info from itself, it also
wants to change its own passwd with yppasswd not the one on the master
server. Unfortunately, the slave server does not run the yppasswd daemon,
and I can't convince the slave server to go and change the passwd on the
master server.
If I try to run the yppasswd daemon on the slave server the change to the
passwd file is not reflected because no make passwd is issued, if the
yppasswd daemon is issued to run make passwd, the passwd is changed on the
slave server only and overwritten the next time the master server's passwd
file is changed.
This product has been around for a while. Is it as baffed as I think, or
is my brain just in Friday afternoon mode.
BTW. The man page nis_intro recommends 3 to 4 servers per NIS domain. I
know why, because if the master server goes down and no slaves are present,
all the clients hang awfully.
My problem would be solved if the slave servers considered them client
of the master and not of themselves. Has anyone managed to set this
up properly?
Thanks in advance.
Dick
Received on Fri May 16 1997 - 22:33:06 NZST