S28NetworkManager simply requires that networkmanager be started. That does NOT guarantee that you have an active network connection. The whole idea behind NM is that it will manage network connection and disconnect for the system, behind the scenes.
What's happening here is that NM comes up and starts trying to bring the network up in the background. In the meantime the init process continues along to the next item to be started. This is the major paradigm shift that NM brings in, but unfortunately it requires that every network service be rewritten to be NM-aware and use dbus so that they can delay starting up until NM tells them the network is available. If they don't do that then there is no way your system can be robust while using NM. ypbind has been modified to speak NM, so as long as NM is properly reporting the network connection status for your system (apparently this is quite difficult to get right, for whatever reason) then NIS should be working OK at this point. However, other network services, most notably autofs (see for example bug #213574 ), do not speak NM, even today (years after it was introduced). So, NM still breaks many enterprise systems. -- 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
