Re: Odd NIS Behavior Following Failure of Slave Server
- From: Chris Cox <ccox_nopenotthis@xxxxxxxxxxx>
- Date: Mon, 12 Mar 2007 10:59:17 -0500
pruettc@xxxxxxxxx wrote:
I have three NIS slaves across three different subnets, each running
Solaris (server1, server2, server3, for ease). I have a number of AIX
5.2 TL7 through TL9 NIS clients that point to these slaves through
their /var/yp/binding/$DOMAIN/ypserves files, with server1 taking
precedence. They are served maps for passwd, group, hosts, and
automounter functions.
Recently, we had a power loss that took down server1. All of the AIX
clients successfully bound to server2 or server3 without problems
after the 60-second timeout we had in place.
When you say you have it configured to unbind and rebind to
a different server after a 60 second timeout, what did you do
to configure this behavior?
It could explain much...
.
- Follow-Ups:
- Re: Odd NIS Behavior Following Failure of Slave Server
- From: pruettc
- Re: Odd NIS Behavior Following Failure of Slave Server
- From: pruettc
- Re: Odd NIS Behavior Following Failure of Slave Server
- References:
- Odd NIS Behavior Following Failure of Slave Server
- From: pruettc
- Odd NIS Behavior Following Failure of Slave Server
- Prev by Date: Re: route
- Next by Date: Re: Odd NIS Behavior Following Failure of Slave Server
- Previous by thread: Re: Odd NIS Behavior Following Failure of Slave Server
- Next by thread: Re: Odd NIS Behavior Following Failure of Slave Server
- Index(es):