SUMMARY: NIS and remote (not well connected) client

From: Debbie Tropiano <>
Date: Thu Feb 05 2004 - 18:40:52 EST
Hello -

Apparently this is indeed the correct answer and, it was recommended
to only include the remote hostname in the file (and not the master).

Thanks to those who replied (and no thanks to the out of office
replies and the flamer).


Original message:
> 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.
+ Debbie Tropiano -- --  +
| 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
Received on Thu Feb 5 18:46:43 2004

This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:43:26 EST