See the attached log. The first ten or so instances are from /etc/init.d/nis in the normal startup sequence. The second-to-last instance is from the beginning of /etc/rc.local. The final instance is from /etc/rc.local immediately before /etc/init.d/nis is run again (successfully).
Note that ypbind doesn't seem to notice that anything's wrong until it fails to resolve the address of the NIS server, at which point it exits. When doing this manually, before I set up the wait-for-DNS-to-come-up loop in /etc/rc.local, I often saw nm-tool report an IP address but no gateway or DNS. ** Attachment added: "nm-tool.log" http://launchpadlibrarian.net/8848948/nm-tool.log -- 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
