From: "Laurent Bercot" <ska-supervision@skarnet.org>
To: Supervision <supervision@list.skarnet.org>
Subject: Re: Readiness notification exemplars
Date: Wed, 01 Apr 2020 17:13:06 +0000 [thread overview]
Message-ID: <em8bdece91-23bc-457a-93a3-d4e567b1c614@elzian> (raw)
In-Reply-To: <20200401162600.GA31582@mail.hallyn.com>
>There are pros and cons, but you are arguing for parsing stdout for a
>text message and/or using pidfiles (written to an fd).
I'm arguing for none of these things.
I'm arguing for daemons to write a newline to a fd of their choice,
which is hardly anything difficult. And hardly anything difficult for
a supervisor to implement (if you're going to say that it's "parsing
stdout", then okay, but the parser fits in 20 lines of C). The fact
that existing daemon behaviours can be used to trigger the mechanism
without modification is a nice bonus that weighted in favor of that
choice, but was hardly the only factor.
>> I still don't think it would be a good idea.
>It might not be. I'm still looking for good reasons why it wouldn't be.
Well I just gave you a full e-mail of reasons why, if they're not good
enough for you, I doubt anything will convince you. :P
--
Laurent
next prev parent reply other threads:[~2020-04-01 17:13 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 [this message]
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
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=em8bdece91-23bc-457a-93a3-d4e567b1c614@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).