Anthony J Placilla wrote:
>
> The startup sequence is determined by the symlinked run control scripts
> in the various directories under /etc/rc.d/
>
> For example on my machine /etc/rc.d/rc3.d/ contains the following line
> to start the network
> S10network
>
> looking deeper you can see that it's symlinked to the actual init script
> [root@ajplacilla rc3.d]# ls -l |grep S10
> lrwxrwxrwx 1 root root 17 Jan 21 08:57 S10network ->../init.d/network
>
> what you can do is find the relevant lines in each rc# dir & edit them
> so pcmcia start before network Your would look something like
> S10pcmcia
> S11network
>
> Make sure you then edit the symlinks that start with K to stop network
> before stopping pcmcia
>
> do that in rc3,4 & 5.d
Better still, in /etc/init.d/network (and the other /etc/init.d
scripts), there's a line
# chkconfig: 2345 10 90
chkconfig uses this to work out what S10network and F90network should
be, and in which runlevels (2, 3, 4, and 5) it should work.
Change the line to
# chkconfig: 2345 12 90
run
chkconfig network reset
and chkconfig will automatically change S10network to S12network
throughout the /etc/rc.d tree. And if you ever decide to temporarily
configure netowrk not to start, then you can use the system tools to
configure it to start again, and it will still have the new number.
Note: It's supposed to be commented. It's aimed at chkconfig, not the
shell that runs network.
HTH,
James.
--
E-mail address: james@ | Legacy (adj):
westexe.demon.co.uk | an uncomplimentary computer-industry epithet that
| means 'it works'.
| -- Anthony DeBoer
