From: Jeff <sysinit@yandex.com>
To: supervision <supervision@list.skarnet.org>
Subject: Re: s6 style "readiness notification" with perpd
Date: Fri, 26 Apr 2019 17:01:51 +0200 [thread overview]
Message-ID: <3049721556290911@iva7-6548a8037c6d.qloud-c.yandex.net> (raw)
In-Reply-To: <emd3019224-9481-434c-875b-6cea34af0c1c@elzian>
26.04.2019, 11:43, "Laurent Bercot" <ska-supervision@skarnet.org>:
> It would certainly be possible for perpd to do the same, as long
> as it stays under the max open file limit - which may reduce the
> maximum possible number of services, but not enough for it to be
> a serious limitation.
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 ?
next prev parent reply other threads:[~2019-04-26 15:01 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 [this message]
2019-04-26 15:28 ` Laurent Bercot
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=3049721556290911@iva7-6548a8037c6d.qloud-c.yandex.net \
--to=sysinit@yandex.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).