From: Brett Neumeier <bneumeier@gmail.com>
To: "Serge E. Hallyn" <serge@hallyn.com>
Cc: Laurent Bercot <ska-supervision@skarnet.org>,
Supervision <supervision@list.skarnet.org>
Subject: Re: Readiness notification exemplars
Date: Tue, 7 Apr 2020 18:03:15 -0500 [thread overview]
Message-ID: <CAGSetNuTKvyYR=vHM9bCeD60+XFOFVUqEmTE6CdosHJL3-HaOw@mail.gmail.com> (raw)
In-Reply-To: <20200404221811.GA4299@mail.hallyn.com>
[-- Attachment #1: Type: text/plain, Size: 487 bytes --]
On Sat, Apr 4, 2020 at 5:18 PM Serge E. Hallyn <serge@hallyn.com> wrote:
> > 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.
>
It's maybe a little heavy-handed, but is there any technical reason not to
just pick an arbitrary FD, like say 3, and just always use that for a
particular daemon?
Cheers,
Brett
--
Brett Neumeier (bneumeier@gmail.com)
next prev parent reply other threads:[~2020-04-07 23:03 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
2020-04-07 23:03 ` Brett Neumeier [this message]
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='CAGSetNuTKvyYR=vHM9bCeD60+XFOFVUqEmTE6CdosHJL3-HaOw@mail.gmail.com' \
--to=bneumeier@gmail.com \
--cc=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).