Dear Steven,
> You might be able to get a clue about what's going wrong by looking
> in /var/log/messages.
I can't see anything about ypservd's problems in the logfile on the NIS
server. The clients get failure of the kind 'yp domain not bound'.
> Independent of why ypserv is dying, you can allow other users to
> nonetheless log onto their machines. Use "ypinit -s <master server>" on
> one or more other computers to make them slave servers. The slave(s) can
> ease the master's load when it's alive, and take over when the master
> dies.
You are right, this should minimize the risk that nothing is working at
all. But neverthelesse I could still run into problems when there are
general problems with the ypserv program.
Urte
--
\|/
@ @
---------------------------------------------------oOO-(_)-OOo-------------
Urte Fuerst
_/_/ _/ _/_/_/ German Aerospace Center DLR
_/ _/ _/ _/ _/
_/ _/ _/ _/ _/ Institute of Aeroelasticity
_/ _/ _/ _/ _/_/ Bunsenstrasse 10
_/ _/ _/ _/_/ D - 37073 Goettingen
_/ _/ _/ _/ _/ Phone: +49 (0)551 709 2432
_/ _/ _/ _/ _/ Fax: +49 (0)551 709 2862
_/_/_/ _/_/_/_/_/ _/ _/ e-mail: [EMAIL PROTECTED]
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
