[clug] What runlevel should bring network up?

Tony Lewis gnutered at yahoo.com.au
Wed Jun 7 05:53:48 GMT 2006

Michael James wrote:
> Debian brings network up in runlevel 2
>  when everything I know waits till 3.

AIUI, these are simply arbitrary, and subject to interpretation (i.e. 
what the OS designed wants to use them for).

> I'm seeing link S15xntpd fail its initial timeset
>  despite being ostensibly behind S08network.
> This suggests that runlevel 2 might be better.

Whatever the problem is, I don't think it's a runlevel issue.  I'd 
suggest you might want to manually run:
    sudo /etc/init.d/xntpd stop
    sudo /etc/init.d/xntpd start
to see if that helps.  For more debugging info, try:
    sudo sh -x /etc/init.d/xntpd stop
    sudo sh -x /etc/init.d/xntpd start

> AFAIK the booting system waits till all services in a level are alive
>  before starting the S scripts in the next.
> So moving network to 2 would guarantee it was up and running
>  before attempting to start any services on it.

No, it enters a runlevel without sequentially going through any others.  
So entering runlevel 2 does not mean it has executed the scripts in 
runlevel 1.

When you change from one runlevel to another, I think the classic 
approach is that the OS should execute all the K* scripts from the 
current runlevel, then all the S* scripts from the new runlevel.  No 
idea how tightly these rules are followed anymore, as most of the time, 
we don't change runlevels like UNIXers used to in the olden days.


More information about the linux mailing list