From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/2539
Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail
From: Jeff <sysinit@yandex.com>
Newsgroups: gmane.comp.sysutils.supervision.general
Subject: Re: s6 style "readiness notification" with perpd
Date: Fri, 26 Apr 2019 17:01:51 +0200
Message-ID: <3049721556290911@iva7-6548a8037c6d.qloud-c.yandex.net>
References: <1122921556241940@sas1-d856b3d759c7.qloud-c.yandex.net> <emd3019224-9481-434c-875b-6cea34af0c1c@elzian>
Mime-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226";
	logging-data="90304"; mail-complaints-to="usenet@blaine.gmane.org"
To: supervision <supervision@list.skarnet.org>
Original-X-From: supervision-return-2129-gcsg-supervision=m.gmane.org@list.skarnet.org Fri Apr 26 17:01:56 2019
Return-path: <supervision-return-2129-gcsg-supervision=m.gmane.org@list.skarnet.org>
Envelope-to: gcsg-supervision@m.gmane.org
Original-Received: from alyss.skarnet.org ([95.142.172.232])
	by blaine.gmane.org with smtp (Exim 4.89)
	(envelope-from <supervision-return-2129-gcsg-supervision=m.gmane.org@list.skarnet.org>)
	id 1hK2MN-000NNi-EX
	for gcsg-supervision@m.gmane.org; Fri, 26 Apr 2019 17:01:55 +0200
Original-Received: (qmail 11368 invoked by uid 89); 26 Apr 2019 15:02:20 -0000
Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm
Original-Sender: <supervision@list.skarnet.org>
Precedence: bulk
List-Post: <mailto:supervision@list.skarnet.org>
List-Help: <mailto:supervision-help@list.skarnet.org>
List-Unsubscribe: <mailto:supervision-unsubscribe@list.skarnet.org>
List-Subscribe: <mailto:supervision-subscribe@list.skarnet.org>
Original-Received: (qmail 11361 invoked from network); 26 Apr 2019 15:02:20 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1556290911;
	bh=CaOTzCxZExWwtgVMgUQAnBEg8BCqIojzescj84Aex+U=;
	h=References:Date:Message-Id:Subject:In-Reply-To:To:From;
	b=rnJSs57Fgc4s3hHdj5bqw60H8ILUab9gtdzL6FWB4KDrB9wn48iViKQUGjzGxQgDp
	 8MSDUKaOxrk1me0NLZf+hkfxynp9akBTOPFsIDjdg4DZsI6VPr0YebDaQcIJvGAkyw
	 QF0G1SIacF38Yahd9CcRVARSwAxHOOAKxvY4uzCI=
Authentication-Results: mxback17o.mail.yandex.net; dkim=pass header.i=@yandex.com
In-Reply-To: <emd3019224-9481-434c-875b-6cea34af0c1c@elzian>
X-Mailer: Yamail [ http://yandex.ru ] 5.0
Xref: news.gmane.org gmane.comp.sysutils.supervision.general:2539
Archived-At: <http://permalink.gmane.org/gmane.comp.sysutils.supervision.general/2539>

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 ?