From: Steve Litt <slitt@troubleshooters.com>
To: supervision@list.skarnet.org
Subject: Re: runit patches to fix compiler warnings on RHEL 7
Date: Thu, 28 Nov 2019 15:39:13 -0500 [thread overview]
Message-ID: <20191128153913.6e96d517@mydesk.domain.cxm> (raw)
In-Reply-To: <em45d91edb-d7ec-463a-b4c4-10f49710c966@elzian>
On Thu, 28 Nov 2019 19:04:37 +0000
"Laurent Bercot" <ska-supervision@skarnet.org> wrote:
> - We on the list will gladly help with any question with runit, but
> to be honest, I'm not exactly sure what to do with patch upstream
> requests for runit. Is anyone processing them and integrating them
> into a new release?
For submitting patches, I'd recommend working with the Void Linux
project. They can be found at #xbps on Freenode IRC. Void Linux has
used runit as their init system for the past 5 years: Their
implementation is very reliable and mature.
>
> - I host this list. I'm also the author of s6, a supervision
> software suite that is very similar to runit in many ways. s6 is
> actively maintained and has a public git repo, and we generally have
> a quick response time with requests.
>
> - My opinion is that the most sustainable path forward, for runit
> users who need a centrally maintained supervision software suite, is
> to just switch to s6 - and it comes with several other benefits as
> well.
IMHO not necessarily. There are people whose top priority is
simplicity. They value simplicity over guaranteeing against a machine
whose supervisor has died, and is now incommunicado. They value
simplicity over PID1's ability to supervise one program; the process
supervisor (did I get that right?). Such people would prefer runit.
Additionally, if a person uses sysvinit as PID1 and only PID1, and puts
"respawn runsvdir" in /etc/inittab, then they do get PID1 supervising
the supervisor.
One other observation: If I wanted the Cadillac of the industry, I'd go
with s6. But on a day to day basis, the Chevy of the industry, runit, is
good enough for the driving I do.
Which leads to the next point: One reason runit has such a large
mindshare is because Void Linux and maybe some others ship with runit
as their init. s6 has an opportunity to leapfrog. Right now, the Devuan
project is discussing supplying run scripts for runit and for s6.
Assuming Debian ship with a working s6 (only has to work as a
supervisor: sysvinit could be PID1), if the s6 run scripts arrive
first, I think s6 would be in a position to become Devuan's default
supervisor a year or two from now. I spoke the preceding sentence as an
individual, not as a member of the Devuan community. Anyway, if you
have a bunch of known-good s6 run (and finish) scripts curated
somewhere, everyone would be pleased if you let the Devuan user mailing
list know where they are.
Thanks,
SteveT
Steve Litt
November 2019 featured book: Manager's Guide to Technical
Troubleshooting Second edition
http://www.troubleshooters.com/mgr
next prev parent reply other threads:[~2019-11-28 20:39 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 21:43 J. Lewis Muir
2019-11-27 20:33 ` J. Lewis Muir
2019-11-28 7:59 ` Ben Franksen
[not found] ` <ecdf4d8f-93f6-3f9f-b84c-351fa91c7f02@uni-bremen.de>
2019-11-28 19:04 ` Laurent Bercot
2019-11-28 20:39 ` Steve Litt [this message]
2019-11-28 22:17 ` runit or s6 (was: runit patches to fix compiler warnings on RHEL 7) Laurent Bercot
2019-11-29 14:09 ` runit patches to fix compiler warnings on RHEL 7 Jan Braun
2019-11-29 21:46 ` Dewayne Geraghty
2019-11-30 1:22 ` Colin Booth
2019-11-30 0:21 ` Colin Booth
2019-11-30 3:14 ` Steve Litt
2019-11-30 13:32 ` Jeff
2019-11-30 13:46 ` Jeff
2019-11-30 10:15 ` s6 usability (was: runit patches to fix compiler warnings on RHEL 7) Laurent Bercot
2019-11-30 14:32 ` Jeff
2019-11-30 18:58 ` Laurent Bercot
2019-12-02 12:07 ` Jeff
2019-12-02 22:20 ` Laurent Bercot
2019-12-02 2:47 ` Steve Litt
2019-12-02 3:37 ` s6 usability Dewayne Geraghty
2019-12-02 10:24 ` fungal-net
2019-12-02 21:32 ` s6 usability (was: runit patches to fix compiler warnings on RHEL 7) Laurent Bercot
2019-12-02 23:17 ` s6 usability Samuel Holland
2019-12-03 22:10 ` Steve Litt
2019-12-21 11:49 ` Jan Braun
2019-12-04 12:15 ` Jonathan de Boyne Pollard
2019-12-04 21:02 ` Laurent Bercot
2019-12-04 1:30 ` s6 usability (was: runit patches to fix compiler warnings on RHEL 7) Casper Ti. Vector
2019-12-21 9:26 ` s6 usability Jan Braun
2019-12-21 18:36 ` Guillermo
2019-12-21 21:19 ` Colin Booth
2019-12-22 1:05 ` Jan Braun
2019-12-22 8:30 ` Colin Booth
2019-12-21 23:46 ` Laurent Bercot
2019-12-22 5:53 ` Jan Braun
2019-12-22 20:33 ` Steve Litt
2019-12-22 23:20 ` Laurent Bercot
2019-12-23 1:28 ` Oliver Schad
2019-12-23 9:14 ` Laurent Bercot
2019-12-23 10:15 ` Jonathan de Boyne Pollard
2019-12-24 0:18 ` Oliver Schad
2019-12-23 1:57 ` Steve Litt
2019-12-23 9:00 ` Laurent Bercot
2019-12-22 23:47 ` Dewayne Geraghty
2019-12-04 11:36 ` runit patches to fix compiler warnings on RHEL 7 Jonathan de Boyne Pollard
2019-12-04 16:40 ` J. Lewis Muir
2019-12-04 20:48 ` Laurent Bercot
2019-12-04 21:32 ` J. Lewis Muir
2019-12-04 21:06 ` Steve Litt
2019-12-04 21:50 ` Laurent Bercot
[not found] ` <20191205132736.7f501460@puter>
2019-12-08 19:10 ` Laurent Bercot
2019-12-02 17:57 ` J. Lewis Muir
2019-12-02 21:06 ` J. Lewis Muir
2019-12-02 22:22 ` Laurent Bercot
2019-12-02 21:58 ` Laurent Bercot
2019-12-03 10:57 ` Benjamin Franksen
2019-12-04 10:43 ` Jonathan de Boyne Pollard
2019-12-02 17:13 ` J. Lewis Muir
2019-12-04 11:13 ` Jonathan de Boyne Pollard
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=20191128153913.6e96d517@mydesk.domain.cxm \
--to=slitt@troubleshooters.com \
--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).