From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/2623 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: "Laurent Bercot" Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: killall test run Date: Sun, 19 May 2019 23:06:39 +0000 Message-ID: References: <11997211556565598@myt6-27270b78ac4f.qloud-c.yandex.net> <20190501033355.6e41e707@mydesk.domain.cxm> <20190515132206.03f9736e@mydesk.domain.cxm> <20190516012214.15ffcf2e@dickeberta> <20190515210717.27b002ba@mydesk.domain.cxm> <5f5b6035-240b-e6d6-497d-d9bb945d135f@obarun.org> <5994381558140755@sas2-2074c606c35d.qloud-c.yandex.net> <57af526d-cc12-135b-218c-721d51129876@obarun.org> <9538981558270634@myt3-c573aa6fc782.qloud-c.yandex.net> Reply-To: "Laurent Bercot" Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="170219"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: eM_Client/7.2.34711.0 To: super Original-X-From: supervision-return-2213-gcsg-supervision=m.gmane.org@list.skarnet.org Mon May 20 01:05:54 2019 Return-path: 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 ) id 1hSUsL-000i9D-8Z for gcsg-supervision@m.gmane.org; Mon, 20 May 2019 01:05:53 +0200 Original-Received: (qmail 29796 invoked by uid 89); 19 May 2019 23:06:17 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm Original-Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Original-Received: (qmail 29789 invoked from network); 19 May 2019 23:06:17 -0000 In-Reply-To: Xref: news.gmane.org gmane.comp.sysutils.supervision.general:2623 Archived-At: >That seems to be the route that Ad=C3=A9lie has taken. With an execline >script, /lib/s6/s6-svscanboot, configured in an /etc/inittab 'respawn' >entry. This results in a supervised s6-svscan (by sysvinit), and a >supervised catch-all logger. Yes. I am also currently working on integrating s6-linux-init into Ad=C3=A9lie in order to have s6-svscan as pid 1, this should be ready some time this week. Users will have a choice between standard sysvinit with a supervised s6 tree (as it is now) and s6-svscan as pid 1. >> i do not know the order >> in which sysvinit processes the inittab entries for a given (SysV) >> "runlevel". do "wait" entries precede "respawn" entries, followed >> by the "once" entries ? >I believe they are processed in line order. Yes, but that is undocumented and shouldn't be relied upon - and there's no readiness notification for "respawn" lines anyway, so relying on order could be racy. For all intents and purposes, all inittab lines after "sysinit" are spawned in parallel or without a specified order. -- Laurent