supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Steve Litt <slitt@troubleshooters.com>
To: supervision@list.skarnet.org
Subject: Re: Can s6 be enough?: was s6-ps
Date: Mon, 7 Jan 2019 16:45:06 -0500	[thread overview]
Message-ID: <20190107164506.0d925cd9@mydesk.domain.cxm> (raw)
In-Reply-To: <CAGSetNsyyZEaOpQfNA_saaFyR9rmBbG0QQU_UR_dhk965tCDyQ@mail.gmail.com>

On Sun, 6 Jan 2019 09:03:33 -0600
Brett Neumeier <bneumeier@gmail.com> wrote:

> 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?
> >  
> 
[snip]
> - 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. 
[snip]
> 
> 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? 

1) Apparently Debian doesn't yet have an s6-rc package

2) s6-rc adds more features and complexity

I don't want to avoid s6-rc. If I had s6, I'd probably use s6-rc. But I
have runit, which at a casual glance is like s6 without s6-rc, and
everything works fine for me.

When Debian acquires a properly working s6-rc package, the answer to my
question degenerates to "why not?" But for now, for the Debian person
who only installs via package, s6-rc is out of the question, so my
question was, isn't s6 itself good enough?

 
SteveT

Steve Litt 
January 2019 featured book: Troubleshooting: Just the Facts
http://www.troubleshooters.com/tjust


  reply	other threads:[~2019-01-07 21:45 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
2019-01-07 21:45         ` Steve Litt [this message]
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=20190107164506.0d925cd9@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).