Same old problem on a fresh 9.04. It boils down to: ypbind is tried at S18nis, NetworkManager starts a lot later at S28NetworkManager. IP connectivity often isn't up after S99, at least if using DHCP.
The problem disappears after configuring the old way via /etc/network/interfaces , thereby shortcutting NetworkManager. Looks like NM introduced having network only a lot later in the startup process; Should affect other network-dependent services similiarly. ypbind's NM integration does not help at all as long NM isn't yet running while it is started (see ypbind manpage). i.e. -no-dbus does not make any difference here... Fix it by having ypbind started after NM without -no-dbus, or via /etc/network/if-up.d/ to ensure we already have net. In case of NIS passwd this creates the possibility of having a temporarily unfunctional login prompt shown, so some user feedback about network connectivity should be introduced there. The startup sequence currently delivered with nis is generally incompatible with Ubuntu Desktop's reliance on NetworkManager for bringing up IP connectivity. One of three things needs to happen: * rework nis startup sequence + handle possible login deferral, or * return to using /etc/network/interfaces at least for some primary interface, or * move nis from main and regard it unsupported g., Filip Moritz -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
