From: "Laurent Bercot" <ska-supervision@skarnet.org>
To: "supervision@list.skarnet.org" <supervision@list.skarnet.org>
Subject: Re: runit SIGPWR support
Date: Mon, 24 Feb 2020 19:53:44 +0000 [thread overview]
Message-ID: <emf679699a-52a7-45a3-aa17-df08e1a8837f@elzian> (raw)
In-Reply-To: <7845971582549235@iva4-35f072fa8e4e.qloud-c.yandex.net>
>in this case systemd compatibility can be trivially achieved,
>so there is no real reason to abstain from it.
"systemd compatibility" makes no sense here. We are talking about
runit or s6 as an init system: by definition, in that context, there
is no systemd, no interaction with systemd, nothing that requires
compatibility with systemd.
If by "compatibility" you mean: doing the same things that systemd
does, following the same API, aligning on its choices, then I have
a question for you: are you also in systemd discussion spaces and
asking them to align on the design choices made by s6? Why not?
>systemd uses real time signals since they were introduced
>for this purpose:
>signals without an already assigned default meaning,
>free for application (ab)use, hence the systemd approach is
>absolutely correct here.
systemd uses a mechanism that it chose, and that works.
sysvinit uses another mechanism, and that works.
busybox init uses another mechanism, and that works.
runit uses another mechanism, and that works.
s6 uses another mechanism, and that works.
What do you have trouble understanding?
>#else
> /* probably OpenBSD */
>#endif
Ah yes, very accurate heuristics, absolutely up to par with my code
quality standards. 10/10, would throw into the garbage bin again.
--
Laurent
next prev parent reply other threads:[~2020-02-24 19:53 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1beb6e35-d4be-60b8-fc52-af666c4fffe3@gmx.com>
2020-02-12 14:25 ` innerspacepilot
2020-02-12 21:54 ` Colin Booth
2020-02-12 22:16 ` Dewayne Geraghty
2020-02-14 9:38 ` Jeff
2020-02-14 12:38 ` Steve Litt
2020-02-15 10:47 ` fungal-net
2020-02-14 10:08 ` Jeff
2020-02-14 10:46 ` Jeff
2020-02-14 12:29 ` innerspacepilot
2020-02-14 12:45 ` Steve Litt
[not found] ` <CALZWFRLvtofWfP4kzxJ8_8_K3nzebPjCR-NsJ2MU22cSuaOLng@mail.gmail.com>
[not found] ` <20200214182241.15614126@mydesk.domain.cxm>
2020-02-17 19:46 ` Cameron Nemo
2020-02-23 16:11 ` Jeff
2020-02-17 14:39 ` Jeff
2020-02-14 14:02 ` Casper Ti. Vector
2020-02-17 14:45 ` Jeff
2020-02-17 14:50 ` Jeff
2020-02-14 13:15 ` Casper Ti. Vector
2020-02-14 13:39 ` innerspacepilot
2020-02-14 13:57 ` Casper Ti. Vector
2020-02-14 14:06 ` innerspacepilot
2020-02-14 14:25 ` Casper Ti. Vector
2020-02-14 18:30 ` Laurent Bercot
2020-02-17 10:00 ` innerspacepilot
2020-02-17 15:13 ` Jeff
2020-02-18 9:39 ` Laurent Bercot
2020-02-20 20:39 ` Serge E. Hallyn
2020-02-23 16:51 ` Jeff
2020-02-23 23:53 ` Laurent Bercot
2020-02-24 6:31 ` innerspacepilot
2020-02-24 10:23 ` Laurent Bercot
2020-02-24 13:00 ` Jeff
2020-02-24 19:53 ` Laurent Bercot [this message]
2020-02-24 13:12 ` innerspacepilot
2020-02-24 15:26 ` Serge E. Hallyn
2020-02-26 8:07 ` innerspacepilot
2020-02-28 6:39 ` Jan Braun
2020-02-28 9:45 ` Alex Suykov
2020-02-28 23:50 ` fungal-net
2020-02-29 13:44 ` Jonathan de Boyne Pollard
2020-02-29 18:20 ` Guillermo
2020-03-06 20:07 ` innerspacepilot
2020-03-06 20:09 ` innerspacepilot
2020-02-25 8:39 ` Jonathan de Boyne Pollard
2020-02-24 21:13 ` Guillermo
2020-02-24 22:25 ` Laurent Bercot
2020-02-24 22:49 ` Laurent Bercot
2020-02-24 23:08 ` Guillermo
2020-02-25 1:48 ` Laurent Bercot
2020-02-25 9:08 ` Jonathan de Boyne Pollard
2020-02-25 18:38 ` Guillermo
2020-03-16 12:49 ` Jeff
2020-03-16 17:13 ` Jeff
2020-02-24 23:03 ` Guillermo
2020-03-16 12:31 ` Jeff
2020-03-16 18:03 ` Laurent Bercot
2020-02-23 17:31 ` Jeff
2020-02-24 0:33 ` Laurent Bercot
2020-02-14 19:08 ` John W Higgins
2020-02-14 23:18 ` Laurent Bercot
2020-02-14 23:38 ` John W Higgins
2020-02-15 2:15 ` Laurent Bercot
2020-04-14 16:57 Maxim Vetsalo
-- strict thread matches above, loose matches on Subject: below --
2020-01-23 20:44 innerspacepilot
2020-01-31 4:39 ` Colin Booth
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=emf679699a-52a7-45a3-aa17-df08e1a8837f@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).