On Wed, Apr 9, 2008 at 4:43 AM, Jesse Keating <jkeating@xxxxxxxxxx> wrote: > > On Tue, 2008-04-08 at 20:03 -0700, David Mack wrote: > > After a kickstart install of the current Rawhide tree, ypbind fails to > > come up because the network is not up at that point in the boot > > process. The /etc/init.d/network script is not being called during the > > boot process. NetworkManager is being invoked later and manages to > > bring up eth0 but it's much too late by that time for NIS, NFS etc. > > After boot, logging in as root, running "chkconfig network on" and > > rebooting fixes this problem. > > > When did you do your install? I do believe we are working to make sure > that NM starts up early enough, or the other services are fixed to be > smart enough to handle a later NM. NM is our default "bring up the > network" service, we won't be reverting back to the 'network' service. Yesterday (April 8). The bug was against initscripts-8.68-1. I just kickstarted the machine again with the same result. In /etc/rc3.d, NetworkManager is started by S99NetworkManager, long after ypbind, rpcbind, sshd, sendmail, etc. initscripts-8.69-1. Dave -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
