From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/2617
Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail
From: Bob <sysinit@yandex.com>
Newsgroups: gmane.comp.sysutils.supervision.general
Subject: Re: emergency IPC with SysV message queues
Date: Sun, 19 May 2019 20:38:24 +0200
Message-ID: <20190519183823.GD4861@panda>
References: <20190509071019.GE4017@panda>
 <em1f23354c-db66-49e8-a561-d73fce7bbbfb@elzian>
 <7911341557578305@sas1-23a37bc8251c.qloud-c.yandex.net>
 <em12162a56-a9bf-476e-9118-e23d2f8b2ce1@elzian>
 <856441558019755@sas1-cd55e40a6ba0.qloud-c.yandex.net>
 <em215c8a88-d142-4c0c-88e7-42cca5581642@elzian>
Reply-To: sysinit@yandex.com
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226";
	logging-data="30289"; mail-complaints-to="usenet@blaine.gmane.org"
User-Agent: Mutt/1.10.0 (2018-05-17)
To: super <supervision@List.skarnet.org>
Original-X-From: supervision-return-2207-gcsg-supervision=m.gmane.org@list.skarnet.org Sun May 19 20:38:32 2019
Return-path: <supervision-return-2207-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-2207-gcsg-supervision=m.gmane.org@list.skarnet.org>)
	id 1hSQha-0007mf-Jd
	for gcsg-supervision@m.gmane.org; Sun, 19 May 2019 20:38:30 +0200
Original-Received: (qmail 18513 invoked by uid 89); 19 May 2019 18:38:56 -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>
List-Id: <supervision.list.skarnet.org>
Original-Received: (qmail 18506 invoked from network); 19 May 2019 18:38:56 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1558291107;
	bh=Z4qCNrzBpdUr9oBzeD1mCIjPqqdSc4MTRxCFYv+5X08=;
	h=In-Reply-To:Reply-To:Subject:To:From:References:Date:Message-ID;
	b=adUsLmrBYwgPqH+GQCnzsXlTqldThZUkXBRRC9Y9UK64fHujqE/P5Xnth5wGpfvne
	 lN7NdkpXU90OSLh3oPBpulwxcL4MBQzsPrl1Y/kwtijVpFBlPJm4K4A71jNTiMskID
	 nSl/DHNAAdfaJnbgtB0JsJJA0HVvYTHcC70vzvQk=
Authentication-Results: mxback15o.mail.yandex.net; dkim=pass header.i=@yandex.com
Content-Disposition: inline
In-Reply-To: <em215c8a88-d142-4c0c-88e7-42cca5581642@elzian>
Xref: news.gmane.org gmane.comp.sysutils.supervision.general:2617
Archived-At: <http://permalink.gmane.org/gmane.comp.sysutils.supervision.general/2617>


BTW:

i assume runit-init was introduced when its author wanted go get rid
of SysV init without changing runsvdir while s6-svscan's signal
handling functionality was motivated by the same desire and previous
hacks that involved running svscan directly as process #1.

this explains their authors' design decisions and the different ways
both took.