>>>
>>>I was talking to a vendor and they suggested that in order to have high
>>>availabliity we should have all of our 140 clients be NIS slaves and bind
>>>to themselves. This would get us around a problem of having an NIS slave go down
>>>then hanging its clients till they rebound to someone else. It certainly makes
>>>me think! Has anyone tried this? If so how would you make a NIS slave
>>>bind only to itself and not let anyone else bind to it. At the same time would
>>>having all machines be NIS slaves create alot of overhead when the maps are
>>>pushed?
>>>
>>>
>>>Regards,
>>>Phil
>>
>>It seems that it would be too much overhead on the pushes.
>>Here were the replies:
>>
>>
>Phil:
>Do you have the book 'Managing NIS and NFS' by Hal Stern of Sun?
>(ISBN 0-937175-75-7 O'Reilly and Assoc.)
>I understand that a single server is able to serve about 20-50
>NIS clients, so about 5 servers would be enough. You could easily
>increase that number to 10 or 15, maybe more, and still have a
>high level of availability, without all the problems you have when
>making every client a server as well.
>Andre++
Andre,
The problem we run into for the setup as you layed out is this.
If you have 50 clients bound to 5 servers, there will be about 10 clients bound
to each server(in real life it would be much more lopsided). If one of these
servers goes down its 10 clients will be hung till they rebind to a different
server. This takes about 10 minutes, which we would like to avoid.
Regards
Phil
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:08:01 CDT