From: Brett Neumeier <bneumeier@gmail.com>
To: Steve Litt <slitt@troubleshooters.com>
Cc: supervision@list.skarnet.org
Subject: Re: Can s6 be enough?: was s6-ps
Date: Sun, 6 Jan 2019 09:03:33 -0600 [thread overview]
Message-ID: <CAGSetNsyyZEaOpQfNA_saaFyR9rmBbG0QQU_UR_dhk965tCDyQ@mail.gmail.com> (raw)
In-Reply-To: <20190105153028.28bc0bab@mydesk.domain.cxm>
[-- Attachment #1: Type: text/plain, Size: 1350 bytes --]
On Sat, Jan 5, 2019 at 2:30 PM Steve Litt <slitt@troubleshooters.com> wrote:
> So what do you all think? Is s6 a useful init system without s6-rc?
>
My 0.02 USD -- based on my experience of setting up a simple GNU/Linux
distribution from the ground up using s6, s6-rc, and s6-linux-init...
- s6-rc provides useful functionality: it is really handy, when defining
the way that the system should start up, to have bundles and oneshots; it
is also really handy to be able to start up or shut down groups of
processes via bundles.
- The cost of using s6-rc is negligible. As installed on my x86_64 system
with documentation, it consumes around 576 *kilobytes* of storage space. It
compiles and installs in substantially less than a minute. Learning how to
craft s6-rc service definition directories is no more difficult than
learning how to craft s6 servicedirs.
- You don't lose any capability provided by s6 if you also use s6-rc. You
can send whatever signals you want to the supervised processes by using
s6-svc directly.
So ... costs ~= 0, benefits > 0, to me the question of whether s6 is useful
_without_ s6-rc is kind of pointless.
I'm inclined to turn the question around: what leads you to want to avoid
s6-rc? Is there some other system that provides more benefits at lower cost?
Cheers!
Brett
--
Brett Neumeier (bneumeier@gmail.com)
next prev parent reply other threads:[~2019-01-06 15:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9f647c4c-2dc3-b977-928c-ee164ba88afe@ntlworld.com>
2019-01-05 0:20 ` s6-ps Laurent Bercot
2019-01-05 4:04 ` s6-ps Jonathan de Boyne Pollard
2019-01-05 10:46 ` s6-ps Jonathan de Boyne Pollard
2019-01-05 14:41 ` s6-ps Jonathan de Boyne Pollard
2019-01-05 15:29 ` s6-ps multiplexd
2019-01-05 20:30 ` Can s6 be enough?: was s6-ps Steve Litt
2019-01-05 21:22 ` Laurent Bercot
[not found] ` <20190106053901.GA16647@latitude.localdomain>
2019-01-06 7:40 ` Laurent Bercot
2019-01-06 15:03 ` Brett Neumeier [this message]
2019-01-07 21:45 ` Steve Litt
2019-01-08 9:19 ` Laurent Bercot
2019-01-05 21:00 ` s6-ps Guillermo
2019-01-06 1:15 ` s6-ps Steve Litt
2019-01-06 7:06 ` s6-ps Colin Booth
2019-01-06 7:30 ` s6-ps Laurent Bercot
2019-01-06 18:07 ` s6-ps 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=CAGSetNsyyZEaOpQfNA_saaFyR9rmBbG0QQU_UR_dhk965tCDyQ@mail.gmail.com \
--to=bneumeier@gmail.com \
--cc=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).