Ah, this looks like Network Manager is crashing or otherwise stopping at some point after ypbind has started. The ypbind code can't cope with that - it assumes that if Network Manager is running at startup it should continue to rely on it. You should be able to check this by running ypbind in debug mode; restarting NIS will mean that it doesn't activate Network Manager support since it isn't running.
This probably ought to be filed against Network Manager as well though as with all these issues ypbind could do better. -- nis client fails to start at bootup https://bugs.launchpad.net/bugs/105648 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
