All my NIS clients point to nismaster.blah.blah.blah
where nismaster is a CNAME in my DNS for the system that's running
the NIS service. It's been like that for nearly 20 years
with no problems. Plus there's an NIS slave server with its
own CNAME of nisslave.blah.blah.blah
I use hostnames and CNAMES instead of IP addresses in case
the actual server has to be moved to a different host and thus
has a new IP address. Don't want to have to go around to all
the NIS clients and re-key the IP address of the NIS server.
- Larry
On 3/3/15 11:39 AM, Antonio Querubin wrote:
On Tue, 3 Mar 2015, P. Larry Nelson wrote:
Modify /etc/nsswitch.conf to switch the order of "files nis" to
"nis files" for passwd, shadow, and group, as I've always done.
Reboot. Boom! It hangs at loopback interface shutdown!
I repeated this many times to be sure, and it happens the same on
every SL6.x node.
Bug or feature? I can't imagine it to be a feature nor can I
fathom what the order of "files" and "nis" in /etc/nsswitch.conf
has to do with the hanging of the loopback interface shutdown.
It's possible that an SL6.x NIS server might correct the situation,
but I have no time right now to spend a week on that not knowing
it would even work.
Comments and suggestions are welcome.
Are you using hostnames instead of IP addresses anywhere in your NIS
config?
Antonio Querubin
e-mail: [email protected]
xmpp: [email protected]
--
P. Larry Nelson (217-244-9855) | IT Administrator
461 Loomis Lab | High Energy Physics Group
1110 W. Green St., Urbana, IL | Physics Dept., Univ. of Ill.
MailTo:[email protected] | http://www.brf-llc.com/lnelson/
-------------------------------------------------------------------
"Information without accountability is just noise." - P.L. Nelson
