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

Bug#727708: Bits from linux.conf.au



On 13/01/14 13:48, Vincent Lefevre wrote:
> On 2014-01-13 13:15:07 +0000, Steven Chamberlain wrote:
>> In the slides[0] 13 to 15, he summarises init systems something like:
>> * SysV - simple, familiar and deterministic
> 
> Deterministic?

Only the traditional SysV.  Debian since squeeze uses startpar so will
start *some* things concurrently (same Sxx number).  And where that
happens, it's much simpler to see/control it as files in /etc/rc2.d,
than e.g. events being triggered and such.

> Well, the scripts may be started sequentially, but this doesn't mean
> that the daemons will be and always in the same order.

Actually, even if they forked in the same order every time, they might
not be *ready* in the same order.  That would be the rationale for
readiness protocols and other features of the more complex init systems.

> In (1):
>   spamd start
>   wicd start/OK
>   sshd start/OK
>   spamd OK
>   postfix start/OK
> 
> In (2):
>   spamd start
>   sshd start/OK
>   wicd start/OK
>   spamd OK
>   postfix start/OK
> 
> This isn't deterministic at all.

I think that's just because insserv+startpar was being used here, not
the traditional SysV.

Regards,
-- 
Steven Chamberlain
steven@pyro.eu.org


Reply to: