I recently moved the NIS master server in my domain to a new
machine(The old machine was bullwinkle, the new machine is sherman).
On most of the machines it worked fine. Almost all of the machines
were able to bind to either the new master or the prexisting slave.
Unfortunetly one of my DECs (Peabody) started having problems and
would not bind to the new server, it insisted on using bullwinkle
(the old server). Eventually peabody became unusable and I was
forced to reboot it. When it came back up it still insisted on using
bullwinkle and again was useless. I eventually turned back on
bullwinkle and was able to get into peabody. I then used ypset to
force it to use sherman (the new server). However when I rebooted
the machine, it again went to bullwinkle. (I then had to turn on the
old server, and use ypset again, to make it useable). Later in the
day (without a reboot) it lost its binding to sherman (the new
server) and again tried to use bullwinkle (the old server).
Does anyone know why peabody insists on going back to the old NIS
server? Is there a Tru64 specific settings file that needs to be
changed?
thanks
James Hammett
----------------------------------------------------------------------------
James Hammett
ACITS (Academic Computing) CPE 4.468
Chemical Engineering Unix Support 471-9701
----------------------------------------------------------------------------
An injustice anywhere is a threat to justice everywhere - MLK jr.
----------------------------------------------------------------------------
Received on Thu Aug 10 2000 - 14:21:06 NZST