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-supervision@skarnet.org>
To: "Carlos Eduardo" <carana2099@gmail.com>,
	"Brett Neumeier" <random@freesa.org>
Cc: supervision <supervision@list.skarnet.org>
Subject: Re: Possible to shut down an s6 service via command rather than signal?
Date: Wed, 24 Jul 2024 21:09:14 +0000	[thread overview]
Message-ID: <eme97c4a62-824e-4752-bc5a-f53bcf59eadb@ab118d7b.com> (raw)
In-Reply-To: <CAN09KnJRt36sc_BCw62u9wmUWr5jiDZLA9Fsm7xW++BqKB10hw@mail.gmail.com>


>From a similar Github issue [1], the suggested way of implementing "stop
>commands" on top of s6 is running these two commands:
>
>```
>s6-svc -O /path/to/service
>stop-command
>```
>
>I'm not aware of any s6-rc sugar around it.

  Indeed.
  Every long-lived program should have a graceful stop signal, instead
of relying on an external command. That's how Unix has always worked,
and it's a misdesign of qemu not to support that.
  Sorry that the s6 way of handling shutdown commands is kludgy, but
s6 really wasn't designed to accommodate them. :/

--
  Laurent


  reply	other threads:[~2024-07-24 21:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-24 17:30 Brett Neumeier via supervision
2024-07-24 18:15 ` Carlos Eduardo
2024-07-24 21:09   ` Laurent Bercot [this message]
2024-07-25  1:15 ` Dewayne Geraghty
2024-07-25 16:26   ` Brett Neumeier via supervision
2024-07-25 16:56     ` Mario Rugiero
2024-07-29 17:29     ` Jan Braun
2024-07-30 19:33       ` Brett Neumeier via supervision

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=eme97c4a62-824e-4752-bc5a-f53bcf59eadb@ab118d7b.com \
    --to=ska-supervision@skarnet.org \
    --cc=carana2099@gmail.com \
    --cc=random@freesa.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).