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 <supervision@list.skarnet.org>
Subject: Re: s6 style "readiness notification" with perpd
Date: Fri, 26 Apr 2019 15:28:30 +0000	[thread overview]
Message-ID: <emf94ce2e1-d197-4203-9413-02c7505d176f@elzian> (raw)
In-Reply-To: <3049721556290911@iva7-6548a8037c6d.qloud-c.yandex.net>

>how is that ?
>what if 2 services (non-interdependent, to be started concurrently)
>specify/use the same fd (number) to write their readiness notification
>message to ? how could perpd tell which of the 2 nofied it ?

  It doesn't matter what the number is that the service sees. As long
as perpd creates a separate pipe for every service (which is why it
would count against the maximum number of services it can maintain),
it can read the notifications from every service separately.

  The notification-fd value used by s6-supervise is not relevant to
s6-supervise, it's only relevant to the service. It's only used
by s6-supervise at ./run spawning time, to tell what number the
*child* should dup2() the notification pipe to before execing ./run,
so the pipe is made available to the service on the fd it expects.
The supervisor itself does not use fixed fd numbers. It would be
the same with perpd.

--
  Laurent



  reply	other threads:[~2019-04-26 15:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-26  1:25 Jeff
2019-04-26  9:24 ` Laurent Bercot
2019-04-26 15:01   ` Jeff
2019-04-26 15:28     ` Laurent Bercot [this message]
2019-04-26 15:58       ` Jeff

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=emf94ce2e1-d197-4203-9413-02c7505d176f@elzian \
    --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).