supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serge@hallyn.com>
To: Laurent Bercot <ska-supervision@skarnet.org>
Cc: Supervision <supervision@list.skarnet.org>
Subject: Re: Readiness notification exemplars
Date: Sat, 4 Apr 2020 17:18:11 -0500	[thread overview]
Message-ID: <20200404221811.GA4299@mail.hallyn.com> (raw)
In-Reply-To: <em4d97f6cd-5c35-44b8-aaaa-87b68f308491@elzian>

On Sat, Apr 04, 2020 at 09:29:04PM +0000, Laurent Bercot wrote:
> 
> > Yes it sounds like I completely misread the earlier emails, sorry about
> > that.  Now, looking at http://skarnet.org/software/s6/notifywhenup.html,
> > I'm probably not reading that quite right, but it seems to tie the
> > proposal to the 'notifcation-fd' file in the service directory, making
> > it a bit less general.
> 
>  The notification-fd file is for s6-supervise, i.e. s6's implementation
> of a supervisor. It is meant to make the fd number configurable on the
> supervisor side, to allow daemons to use whatever fd they choose.
> 
>  On the daemon side, you can use any option you like to tell the daemon
> what fd it should write to. It has nothing to do with s6, and I have no
> recommended policy for daemons.
> 
> 
> >   s6-log however uses the -d argument to pass the
> > fd, so I'll go with that.
> 
>  -d works for s6-log and a few others of my programs. For others, -d
> is already used for something else, so I use another option.
>  I really suggest you don't try to standardize a way to tell daemons
> what fd to use. No method will be universal, there will always be
> some obscure daemon that will conflict with it.
> 

Right, I didn't mean -d specifically :)  I just meant pass the fd# as
a command line argument.

thanks,
-serge


  reply	other threads:[~2020-04-04 22:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-01 13:23 Brett Neumeier
2020-04-01 13:36 ` Casper Ti. Vector
2020-04-01 14:21 ` Serge E. Hallyn
2020-04-01 15:06   ` Laurent Bercot
2020-04-01 15:28     ` Serge E. Hallyn
2020-04-01 15:59       ` Laurent Bercot
2020-04-01 16:26         ` Serge E. Hallyn
2020-04-01 17:13           ` Laurent Bercot
2020-04-04 15:02             ` Serge E. Hallyn
2020-04-04 15:54               ` Laurent Bercot
2020-04-03  7:41           ` Jonathan de Boyne Pollard
2020-04-04 15:48             ` Serge E. Hallyn
2020-04-04 21:29               ` Laurent Bercot
2020-04-04 22:18                 ` Serge E. Hallyn [this message]
2020-04-07 23:03                   ` Brett Neumeier
2020-04-08 11:02                     ` Laurent Bercot
2020-04-09 10:31                     ` Jonathan de Boyne Pollard
2020-04-01 14:55 ` Laurent Bercot

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=20200404221811.GA4299@mail.hallyn.com \
    --to=serge@hallyn.com \
    --cc=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).