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: "supervision@list.skarnet.org" <supervision@list.skarnet.org>
Subject: Re: s6-rc: oneshot services do not get their name as arg 1
Date: Sun, 03 Nov 2024 21:57:32 +0000	[thread overview]
Message-ID: <em44cd76a5-e26d-4bb2-930e-962d435a389f@29a541ad.com> (raw)
In-Reply-To: <1d5e61fc-807f-48d8-8721-1194f3a5338a@sopka.ch>


>I am wondering why oneshot services do not get their names passed as argument 1, while longruns do.
>Is there a reason for that? If yes, what is it? If not, will this be added?

  Longruns being passed their names as argument is a recent addition:
it was useful to implement dynamic instances in s6. It's a pure s6
feature, not an s6-rc one; it just so happens that a longrun's name in
s6-rc translates to the service directory's name in s6.

  Oneshots aren't being handled by s6, so they did not benefit from that
change. They're only run at the s6-rc level, and s6-rc does not pass
service names as arguments.

  There would be no benefit to doing that, because oneshots do not have
instances, so any up or down script knows exactly what service it is
starting or stopping.

--
  Laurent


  reply	other threads:[~2024-11-03 21:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-03 21:46 Paul Sopka
2024-11-03 21:57 ` Laurent Bercot [this message]
2024-11-03 22:16   ` Paul Sopka
2024-11-04  0:17     ` Re[2]: " Laurent Bercot
2024-11-04  7:18       ` Paul Sopka

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=em44cd76a5-e26d-4bb2-930e-962d435a389f@29a541ad.com \
    --to=ska-supervision@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).