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" <ska-skaware@skarnet.org>
To: "skaware@list.skarnet.org" <skaware@list.skarnet.org>,
	"supervision@list.skarnet.org" <supervision@list.skarnet.org>
Subject: [announce] s6-2.9.2.0
Date: Tue, 16 Jun 2020 20:41:44 +0000	[thread overview]
Message-ID: <em4caae75b-6e96-4209-97da-f84b52ef0a7d@elzian> (raw)


  Hello,

  s6-2.9.2.0 is out.

  This release is happening a lot earlier than I intended, but I made a
mistake: I released s6-linux-init-1.0.4.1 (a bugfix version) and it
depends on the new feature of s6-2.9.2.0. So, in order to keep the
latest versions in sync, I have to release s6-2.9.2.0 now.

  The new feature is the addition of the -d option to s6-sudod, to
allow a server to "detach" from the client and not die if the client
disappears.

  This is important for s6-linux-init because the shutdown procedure is
handled by the runleveld service, which is really a s6-rc invocation
behind s6-sudod, and if the shutdown procedure is triggered from a
xterm that gets killed, without a detaching feature this kills the
s6-rc process and stops the shutdown. The new -d option is meant to
prevent this, and is used in s6-linux-init-1.0.4.1.

  s6-2.9.2.0 also comes with a batch of various documentation fixes
and clarifications requested by several users, who deserve all the
praise for actually helping me improve the doc. :)

  https://skarnet.org/software/s6/
  git://git.skarnet.org/s6

  Enjoy,
  Bug-reports welcome.

--
  Laurent


                 reply	other threads:[~2020-06-16 20:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=em4caae75b-6e96-4209-97da-f84b52ef0a7d@elzian \
    --to=ska-skaware@skarnet.org \
    --cc=skaware@list.skarnet.org \
    --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).