supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "Laurent Bercot" <>
To: "Xavier Stonestreet" <>,
Subject: Re: s6-permafailon not acting as expected
Date: Wed, 18 Nov 2020 18:35:09 +0000	[thread overview]
Message-ID: <em83a2e2b2-2520-4477-b048-853528b894a0@elzian> (raw)
In-Reply-To: <>

>Sounds good. So what kind of interface changes should we expect? I
>mean will they require updating the service definitions, run/finish
>scripts, that sort of thing?

  (Sorry, I missed it indeed.)

  Nothing that drastic; service definitions will not change. They are the
core of s6, and such a change would warrant a lifetime version bump,
I think.

  No, the next release will be about a long overdue cleanup of s6-svscan
and s6-svscanctl invocations: command-line options will change, and
default semantics of signals received by s6-svscan will also change.

  The point is to remove some clutter that is either:
  - legacy behaviours from daemontools's svscan that have not shown they
were useful
  - ad-hoc stuff that was added to support early iterations of running
s6-svscan as pid 1, and that isn't used anymore (in part thanks to the
existence of s6-linux-init 1.x)
  - options that experience has shown to be traps (i.e. ideas that seem
good at first but really encourage bad patterns)

and make the s6-svscan/ctl system less confusing to new users by only
keeping a few relevant and useful configuration switches.
  There will also be QoL improvements to s6-svscan for people who like
to nest supervision trees; also, no promises, but I may come up with
some way to officially support user trees, which are a relatively
common request.


      reply	other threads:[~2020-11-18 18:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-16 18:01 Xavier Stonestreet
2020-11-16 22:05 ` Laurent Bercot
2020-11-17 15:32   ` Xavier Stonestreet
2020-11-17 18:43     ` Xavier Stonestreet
2020-11-17 20:06       ` Xavier Stonestreet
2020-11-17 21:42       ` Laurent Bercot
2020-11-18 17:22         ` Xavier Stonestreet
2020-11-18 18:35           ` Laurent Bercot [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=em83a2e2b2-2520-4477-b048-853528b894a0@elzian \ \ \ \

* 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).