From: "Laurent Bercot" <ska-supervision@skarnet.org>
To: "John W Higgins" <wishdev@gmail.com>, supervision@list.skarnet.org
Subject: Re: runit SIGPWR support
Date: Sat, 15 Feb 2020 02:15:25 +0000 [thread overview]
Message-ID: <em061c1d35-7540-4ada-972f-800095a6820f@elzian> (raw)
In-Reply-To: <CAPhAwGz5N2Gg23QQYswOo6SOSZF4CSZ4B_wn+v=7O4obRAHZ+g@mail.gmail.com>
>I don't generally question people that are this far above my weight class
>on a topic - but I'm pretty sure this [1] implies that pid 1 is not a
>requirement.
Of course, you can run runsvdir directly under a different init. But
that requires a bit of work: you now need to find another way to run
your stage 1, and also your stage 3 when shutting down the container.
Stages 1 and 3 are an integral part of using runit as an init system
instead of just a supervision mechanism (which the runsvdir invocation
in stage 2 is), so if you can't run them because you can't run the
runit binary because it's not pid 1, you need to work around that. And
it's not entirely trivial; to accomplish something similar in s6, I had
to write a whole specific package, s6-linux-init.
innerspacepilot wants to use runit with the least possible amount of
effort, so rewriting a significant portion of the init sequence doesn't
sound like a good match. ;)
>I'm also confused why my suggestion would be put down so harshly outside of
>the possible pid 1 issue.
Sorry if I appeared hostile, that was not my intention; I tend to be
blunt and terse when something seems obvious to me. I just wanted to
stress that any alternative solution to changing the lxc config will
be more costly, one way or another.
--
Laurent
next prev parent reply other threads:[~2020-02-15 2:15 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
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 [this message]
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=em061c1d35-7540-4ada-972f-800095a6820f@elzian \
--to=ska-supervision@skarnet.org \
--cc=supervision@list.skarnet.org \
--cc=wishdev@gmail.com \
/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).