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: Can s6 be enough?: was s6-ps
Date: Sat, 5 Jan 2019 15:30:28 -0500	[thread overview]
Message-ID: <20190105153028.28bc0bab@mydesk.domain.cxm> (raw)
In-Reply-To: <f54a9d22-567a-f238-eae3-915280745c26@NTLWorld.COM>

On Sat, 5 Jan 2019 10:46:29 +0000
Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM>
wrote:


> s6 and s6-rc are actually ports/packages in FreeBSD and s6 is a
> package in Debian.  Alas, the Debian world has not yet caught up with
> the other toolsets, and the third-party Debian packaging for
> s6-linux-utils and the others has yet to make it into Debian's own
> repository.

This brings up a question I've had for a long time. Three years ago I
constructed an init consisting of Suckless Init as PID1 and s6 as the
supervisor, which was called at the end of a simple rc file forked by
Suckless Init. It worked just fine, without s6-rc or any other s6
products.

From discussions with Laurent I got the idea that the main added
functionalities of s6-rc are:

1) Process ordering during boot
2) Ability to intermix longruns with oneshots

Everybody appreciates the preceding two features, but personally, I
don't think they're absolutely necessary. Runit has neither, yet it
works just fine for most things. When I first switched to runit, with
its indeterminate ordering, I figured that with the dependencies I
built into the run scripts,  boot would resemble a field of mousetraps
throwing ping pong balls. But that wasn't the case: runit brought
everything up quickly and without trouble.

So I'm thinking that although process ordering and intermixing are
features we'd everyone likes, all but the most discerning among us
could get along without them and therefore init with s6 alone.

This is more than theoretical. As you remember, Debian's runit package
manager wrote to ask about a minor problem with too many .u files and
was contemplating changing some code, but nobody knew the code
intimately, and runit is pretty much unmaintained at this point. So I
suggested s6, which apparently has a Debian package but not one for
s6-rc. My opinion is one can boot just fine with s6 alone, as long as
you're willing to forego startup ordering and intermixing of longruns
and oneshots, which by definition a runit fan is.

So what do you all think? Is s6 a useful init system without s6-rc?

Thanks,
 
SteveT

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


  parent reply	other threads:[~2019-01-05 20:30 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     ` Steve Litt [this message]
2019-01-05 21:22       ` Can s6 be enough?: was s6-ps 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
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=20190105153028.28bc0bab@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).