I have a NIS+ master server that's been running for a couple months. I just
created a replica server. If I do a "nisping <domainname>" on the master
server, or the replica server, or any of the clients; they all show the
master and replica servers.
But if I reboot the master server, everyone hangs untill it's back up.
Nothing seems to switch to the replica server. I assumed the switch would be
automatic and transparent from the master to a replica. Yes / No ?
What I found out was that NIS+ will NOT use a replica server if you have
password ageing turned on. I ended up using the nistbladm command to change
the shadow field for each user in the password table to turn password-ageing
off temporarily. Because of what this NIS+ domain is used for, that wasn't a
problem. I was then able to halt the master server box and the clients would
use the replica server for logins after that. If seemed to take a minute the
first time on each client (I figured the client had to first figure out the
old NIS+ master was down, then ask the replica) but after that it was fine.
Thanks for the replys and for the help from SunSolve and for the command
wandering I ended up doing to find something that worked. 8-)
U BEFORE POSTING please READ the FAQ located at
. and the list POLICY statement located at
A To submit questions/summaries to this list send your email message to:
A To unsubscribe from this list please send an email message to:
E and in the BODY type:
R unsubscribe sun-managers
. unsubscribe sun-managers email@example.com
L To view an archive of this list please visit:
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:14:21 CDT