Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!news2.arglkargh.de!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Tim Watts <tw_usenet@dionic.net>
Newsgroups: comp.os.linux.misc
Subject: Re: What distros *don't* use systemd ?
Date: Mon, 08 Sep 2014 21:21:54 +0100
Lines: 39
Message-ID: <2of1eb-4ag.ln1@squidward.local.dionic.net>
References: <lu5np1$u6d$2@dont-email.me>	<op.xlk6ccdqa3w0dxdave@hodgins.homeip.net>	<luis5e$v1h$3@dont-email.me>	<p9tvdb-ptn.ln1@squidward.local.dionic.net>	<lukfpv$ht3$2@dont-email.me>	<l121eb-n68.ln1@squidward.local.dionic.net>	<lukpo4$or$3@dont-email.me>	<6o71eb-dgc.ln1@squidward.local.dionic.net> <luku5v$eri$2@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net XsN+5+ff+4nk+UK4GanxTAlKJois6Q2JLACCGwrQa4YxVGoGCq
X-Orig-Path: squidward.local.dionic.net!not-for-mail
Cancel-Lock: sha1:QWe4XJbVZ1EoQTGUvmQHOEpIqUY=
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
In-Reply-To: <luku5v$eri$2@dont-email.me>
Xref: csiph.com comp.os.linux.misc:12047

On 08/09/14 19:57, Dan Espen wrote:

> Without being an expert, sysvinit handles devices at system power up,
> changing init level and system power down.

Yes - and a special case of gettys[1]

> If there is a way to make it handle devices just plugged in, it's not
> clear.

No because that's not its job - that belongs to something else like udev[2].

> Those scripts, mostly obey "start", "stop".  Some also obey "restart",
> and "load".  Without reading the documentation or the shell script there
> is no way to tell.

Generally most of the scripts if run with no args will list their args.

"restart" and "reload" should be standard - restart equating to "stop - 
pause - start" and "reload" where practical signals the daemon to reread 
its config and close/reopen log files (often via a kill -HUP).

[1] Whcih arguably is a bit of a historic oddity, which whilst still 
used is not as important as it once was.

[2] udev is not unique - it could be replaced by any userspace daemon 
listening for kernel messages.


> Many of those scripts must be executed in sequence.  During boot up,
> everything is controlled by the numbers in the symlinks.  Later on, when
> you might want to restart 2 scripts in a sequence, you are out of luck.

If you are doing it manually, what's the problem?

> Running everything sequentially is slow.
>

But not so you'd notice on most systems these days...