This bug has caused me a lot of confusion; on some machines the
YPBINDARGS=-no-dbus worked, on others it did not.  Moving the positions
of startup scripts provided inconsistent results.  It does not seem to
be a NIS bug at all, but is something to do with NetworkManager taking
too long to start (confirmed by putting a call to nm-tool in
/etc/rc.local).  The only consistent solution for me was to follow a
trick in a NetworkManager posting on bug #50430 to put a file containing
the two lines:

#!/bin/sh
invoke-rc.d --quiet nis restart &

into /etc/network/if-up.d

This has been a show-stopper of a bug for me until now, but I'm eager to
upgrade to 8.04LTS, and with support for 7.04 expiring this month had
been desperate to change.  Unsurprisingly, users would not budge until
they could login to their PCs after a reboot.  I'm not a computer expert
at all and therefore has taken me a while to sort out a workaround, and
am surprised that this crippler of a bug seems to have an importance of
"low".  It has been sufficiently serious for some of our users to give
up with Ubuntu and go to other distros.

-- 
nis daemon fails to attach to domain the first time it is run in Gutsy
https://bugs.launchpad.net/bugs/152794
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to