Red Hat Bugzilla – Bug 477045
ypbind hangs at boot time when NetworkManager is turned on
Last modified: 2009-02-13 10:31:16 EST
Description of problem: ypbind hangs at boot time when NetworkManager is turned on Version-Release number of selected component (if applicable): NetworkManager-0.7.0-0.12.svn4326.fc10.i386 How reproducible: Always Steps to Reproduce: 1.Turn on NetworkManager with ntsysv 2.Turn on ypbind with ntsysv 3.Reboot computer Actual results: ypbind hangs for many minutes during bootup and eventually the computer starts up with ypbind not running Expected results: ypbind should start up normally Additional info: ypbind starts normally when network is used instead of NetworkManager. Also, even though NetworkManager and ypbind have S27 for startup, NetworkManager defintely starts up first. Network has S10 for startup and moving NetworkManager to S10 does not fix this problem.
Same issue with nfslock and messagebus. Network manager starts to late in the boot process.
What levels do nfslock and ypbind start at? They'll need to start somewhat later, or we need to switch to a startup dependency system that can handle this stuff.
Chkconfig says nfslock starts at levels 2345. This box has ldap authentication and an nfs home directory. I was able to work around by adding network to runlevels 2345 and disabling NetworkManager.
Ok; I think we'll simply have to revisit this when our startup process gets more intelligent, and we can actually make stuff like ypbind wait on the network actually coming up.