Re: The network init.d wont run at startup
- From: Allen Kistler <ackistler@xxxxxxxxx>
- Date: Wed, 29 Oct 2008 09:37:11 -0500
lovecreatesbeauty@xxxxxxxxx wrote:
On the Fedora 10 Beta, the network and samba function are not ready
after startup, unless I issue the following two pieces of command
manually:
$ su -c '/etc/init.d/network restart'
$ su -c '/etc/init.d/smb restart'
Why do these startup scripts fail to run at boot time, and how to
correct it? The dmesg and network-scripts say so:
$ dmesg | grep eth
eth0: registered as PCnet/PCI II 79C970A
$ grep ONBOOT /etc/sysconfig/network-scripts/ifcfg-eth0
ONBOOT=yes
$
The default way to start networking in Fedora is now by using NetworkManager. The network init script is provided only for backwards compatibility. If you don't use NetworkManager, then you need to configure the run levels for the network init script by using chkconfig.
Personally I prefer the init script, too, but with the direction being not to use the init script, it seems likely that the init script will be gone entirely in F11 (and hence probably RHEL6, which will probably form the base for RHEL6).
.
- Follow-Ups:
- Re: The network init.d wont run at startup
- From: John Oliver
- Re: The network init.d wont run at startup
- From: Allen Kistler
- Re: The network init.d wont run at startup
- References:
- The network init.d wont run at startup
- From: lovecreatesbeauty@xxxxxxxxx
- The network init.d wont run at startup
- Prev by Date: Re: how to compare X Ghz processor to Y Ghz processor?
- Next by Date: Re: The network init.d wont run at startup
- Previous by thread: Re: The network init.d wont run at startup
- Next by thread: Re: The network init.d wont run at startup
- Index(es):