Re: network problems after installation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.

-- 
Jesse Keating
Fedora -- All my bits are free, are yours?

Attachment: signature.asc
Description: This is a digitally signed message part

-- 
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe: 
https://www.redhat.com/mailman/listinfo/fedora-test-list

[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux