NIS and remote (not well connected) client
From: Debbie Tropiano (debbie_at_icus.com)
To: firstname.lastname@example.org Date: Wed, 4 Feb 2004 13:23:27 -0600 (CST)
I have an NIS client that's not well connected to the NIS master
(as in, only via dialup various times during the day). This client
is also a slave server. Recently a reboot was done, but the system
wouldn't come up until connectivity was established with the NIS master.
There were also repeated "NIS server not responding for domain ..."
errors in the /var/adm/messages file.
So I'm assuming that during the process of binding to one of the hosts
listed in the /var/yp/binding/msn/ypservers file it required the network
connection. Would a valid "fix" be to have it bind to itself (since it
is a slave server)? And, if so, would that be implemented by putting its
own hostname as the first entry in the /var/yp/binding/msn/ypservers file?
BTW This is with Solaris 9, but I doubt that it matters much.
Obviously I still find some of the details of NIS a bit of a mystery.
Thanks for any help,
-- + Debbie Tropiano -- email@example.com -- http://www.icus.com/personal.html + | Mommy to Nathan b: 8/17/1995, ^Sara^ b: 10/25/2000 d: 11/7/2000 & | | Leah b: 10/17/2001 a: 9/26/2002 "God shows His opposition to cancer and | | birth defects, not by eliminating them or making them happen only to bad | | people (He can't do that), but by summoning forth friends and neighbors | + to ease the burden and to fill the emptiness." -- Harold S. Kushner + _______________________________________________ sunmanagers mailing list firstname.lastname@example.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers