From: "Laurent Bercot" <ska-supervision@skarnet.org>
To: super <supervision@list.skarnet.org>
Subject: Re: killall test run
Date: Sun, 19 May 2019 23:06:39 +0000 [thread overview]
Message-ID: <emf00a622c-377c-420f-b975-7119fa84cf60@elzian> (raw)
In-Reply-To: <CADQ2Nw99kHULnJGMuPyNaQTJKt30AoLPeCJU2OpTDzP_a3UHUg@mail.gmail.com>
>That seems to be the route that Adélie has taken. With an execline
>script, /lib/s6/s6-svscanboot, configured in an /etc/inittab 'respawn'
>entry. This results in a supervised s6-svscan (by sysvinit), and a
>supervised catch-all logger.
Yes. I am also currently working on integrating s6-linux-init into
Adélie in order to have s6-svscan as pid 1, this should be ready
some time this week. Users will have a choice between standard
sysvinit with a supervised s6 tree (as it is now) and s6-svscan as
pid 1.
>> i do not know the order
>> in which sysvinit processes the inittab entries for a given (SysV)
>> "runlevel". do "wait" entries precede "respawn" entries, followed
>> by the "once" entries ?
>I believe they are processed in line order.
Yes, but that is undocumented and shouldn't be relied upon - and
there's no readiness notification for "respawn" lines anyway, so
relying on order could be racy. For all intents and purposes, all
inittab lines after "sysinit" are spawned in parallel or without a
specified order.
--
Laurent
next prev parent reply other threads:[~2019-05-19 23:06 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 19:19 interesting claims Jeff
2019-04-30 2:49 ` Guillermo
2019-04-30 8:22 ` Laurent Bercot
2019-05-03 0:53 ` what init systems do you use ? Jeff
2019-05-11 18:45 ` Guillermo
2019-05-13 19:13 ` multiplexd
2019-05-13 20:36 ` Laurent Bercot
2019-05-13 21:09 ` Steve Litt
2019-05-14 2:34 ` Guillermo
2019-05-13 21:16 ` Joshua Ismael Haase Hernández
2019-05-14 5:50 ` Colin Booth
2019-05-14 7:15 ` eric vidal
2019-04-30 8:47 ` interesting claims Jonathan de Boyne Pollard
2019-05-01 7:26 ` Steve Litt
2019-05-01 7:33 ` Steve Litt
2019-05-01 18:13 ` Laurent Bercot
2019-05-15 17:22 ` Steve Litt
2019-05-15 23:22 ` Oliver Schad
2019-05-16 1:07 ` Steve Litt
2019-05-16 5:36 ` fungal-net
2019-05-16 8:32 ` Laurent Bercot
2019-05-16 17:10 ` Jeff
2019-05-17 0:23 ` Dewayne Geraghty
2019-05-17 11:21 ` fungal-net
2019-05-17 22:57 ` Guillermo
2019-05-18 0:52 ` Jeff
2019-05-18 16:26 ` fungal-net
2019-05-18 20:04 ` Guillermo
2019-05-19 11:24 ` fungal-net
2019-05-19 12:57 ` killall test run Jeff
2019-05-19 17:29 ` Colin Booth
2019-05-19 20:39 ` Guillermo
2019-05-19 23:06 ` Laurent Bercot [this message]
2019-05-19 20:35 ` interesting claims Guillermo
2019-05-03 1:37 ` how to handle system shutdown ? Jeff
2019-05-03 19:25 ` Laurent Bercot
2019-05-05 0:52 ` is it required to call kill() from process #1 ? Jeff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=emf00a622c-377c-420f-b975-7119fa84cf60@elzian \
--to=ska-supervision@skarnet.org \
--cc=supervision@list.skarnet.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).