The NIS failure is obviously highly visible since it does not fail
gracefully (i.e. it will not magically fix itself once the network is
up) and it prevents you from logging in, but this is not just a NIS
issue; it affects anything that requires a working network connection
and / or DNS to start (NTP; LDAP; autofs, if you use NIS or LDAP maps).
I use the following hack in /etc/rc.local:
echo -n "Waiting for network to come up..."
while :; do
nm-tool | egrep -q 'DNS:[[:space:]]+[1-9]' && break
sleep 1
echo -n "."
done
echo " OK"
/etc/init.d/ntp restart
/etc/init.d/nis restart
/etc/init.d/autofs restart
Just checking for an IP address will not work, because nm-tool reports a
valid IP address almost immediately, but it takes almost a minute for
DNS to show up. I have no idea why DHCP is so slow on this network.
--
NIS has problems starting before the network comes up
https://bugs.launchpad.net/bugs/50430
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
