From: Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM>
Cc: Supervision <supervision@list.skarnet.org>
Subject: Re: Readiness notification exemplars
Date: Fri, 3 Apr 2020 07:41:25 +0000 [thread overview]
Message-ID: <2771eb82-9e19-06a7-d15c-28633971d8b2@NTLWorld.COM> (raw)
In-Reply-To: <20200401162600.GA31582@mail.hallyn.com>
Serge E. Hallyn:
> If making changes to daemons were going to palatable, [...]
>
Clearly, it *is* palatable, given that a few people have been adding the
systemd mechanism to their programs for several years, now.
Pierre-Yves Ritschard's code and Cameron Norman's code come straight out
of actual service programs.
Serge E. Hallyn:
> you are arguing for parsing stdout for a text message and/or using
> pidfiles (written to an fd)
>
No, M. Bercot is not. Quite the opposite, in fact. The s6 readiness
mechanism demands *neither* pidfiles *nor* standard output. It's *any*
file descriptor (as defined by the service), and *just a linefeed*
followed by closing the descriptor.
I'm nodding at almost everything M. Bercot is saying here, by the way.
* http://jdebp.uk./FGA/unix-daemon-readiness-protocol-problems.html
next prev parent reply other threads:[~2020-04-03 7:41 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 [this message]
2020-04-04 15:48 ` Serge E. Hallyn
2020-04-04 21:29 ` Laurent Bercot
2020-04-04 22:18 ` Serge E. Hallyn
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=2771eb82-9e19-06a7-d15c-28633971d8b2@NTLWorld.COM \
--to=j.deboynepollard-newsgroups@ntlworld.com \
--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).