Re: The network init.d wont run at startup
- From: Allen Kistler <ackistler@xxxxxxxxx>
- Date: Wed, 29 Oct 2008 22:25:44 -0500
lovecreatesbeauty@xxxxxxxxx wrote:
On Oct 29, 7:38 pm, Bill Marcum <marcumb...@xxxxxxxxxxxxx> wrote:On 2008-10-29, lovecreatesbea...@xxxxxxxxx <lovecreatesbea...@xxxxxxxxx> wrote:On the Fedora 10 Beta, the network and samba function are not readyYou have a set of directories /etc/rc?.d or /etc/init.d/rc?.d, one for
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
$
each runlevel. Inside those directories are symbolic links with names
that begin with S or K and a number. You might need to increase the
numbers on the S??network and S??smb links.
The Fedora is started in runlelvel 3. Therer're these startup scripts
shown in the following. Same records exist in /etc/rc5.d/ directory.
Do the files with name beginning with `K' mean the functions aren't
invoked at startup? Do I change the K to S and how to deal with the
two digits following the S letter?
Links that start with K are invoked with the "stop" argument when the level is entered. Links that start with S are invoked with the "start" argument when the level is entered. Use the chkconfig command rather than manually creating links to configure what scripts run at what levels.
$ ls -l /etc/rc3.d/ | grep [Nn]etwork
lrwxrwxrwx 1 root root 17 2008-10-29 01:55 K90network -> ../init.d/
network
lrwxrwxrwx 1 root root 24 2008-10-29 02:12 S27NetworkManager -> ../
init.d/NetworkManager
$ ls -l /etc/rc3.d/ | grep smb
lrwxrwxrwx 1 root root 13 2008-10-29 02:10 K35smb -> ../init.d/smb
$
To see what runs when, you can also use chkconfig.
$ /sbin/chkconfig --list
or
# chkconfig --list
To remove NetworkManager, if that's what you really want to do, as root do:
# rpm -e NetworkManager
but then you'll need to use the network init script. Since you have NetworkManager installed, I'd say that you don't have it configured correctly. It's mostly intended for laptops and choosing between wired and wireless cards, anyway, so you can yank it for a server. I do, although, as I posted before, someday soon we aren't going to be able to avoid it, I think. You might have to yank a few things that depend on it, too, if rpm complains about dependencies. Alternatively to leave it installed and turn it off, as root do:
# chkconfig NetworkManager off
To configure the network init script to start the network (if you remove NetworkManager or turn it off) in runlevels 2, 3, 4, and 5, as root do:
# chkconfig --levels 2345 network on
To configure the smb init script to start sharing (looks like you need to do it, anyway) in runlevels 3, 4, and 5, as root do:
# chkconfig --levels 345 smb on
HTH
.
- Follow-Ups:
- Re: The network init.d wont run at startup
- From: lovecreatesbeauty@xxxxxxxxx
- Re: The network init.d wont run at startup
- References:
- The network init.d wont run at startup
- From: lovecreatesbeauty@xxxxxxxxx
- Re: The network init.d wont run at startup
- From: Bill Marcum
- Re: The network init.d wont run at startup
- From: lovecreatesbeauty@xxxxxxxxx
- The network init.d wont run at startup
- Prev by Date: Re: The network init.d wont run at startup
- Next by Date: Re: use what UUID to boot new kernel in menu.lst
- 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):
Relevant Pages
|