From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 19993 invoked from network); 18 Nov 2020 18:35:12 -0000 Received: from alyss.skarnet.org (95.142.172.232) by inbox.vuxu.org with ESMTPUTF8; 18 Nov 2020 18:35:12 -0000 Received: (qmail 31393 invoked by uid 89); 18 Nov 2020 18:35:36 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Received: (qmail 31386 invoked from network); 18 Nov 2020 18:35:36 -0000 From: "Laurent Bercot" To: "Xavier Stonestreet" , supervision@list.skarnet.org Subject: Re: s6-permafailon not acting as expected Date: Wed, 18 Nov 2020 18:35:09 +0000 Message-Id: In-Reply-To: References: Reply-To: "Laurent Bercot" User-Agent: eM_Client/8.0.3385.0 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: -100 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedujedrudefhedguddufecutefuodetggdotffvucfrrhhofhhilhgvmecupfgfoffgtffkveetuefngfdpqfgfvfenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhephffvufffkfgjfhhrfgggtgfgsehtqhertddtreejnecuhfhrohhmpedfnfgruhhrvghnthcuuegvrhgtohhtfdcuoehskhgrqdhsuhhpvghrvhhishhiohhnsehskhgrrhhnvghtrdhorhhgqeenucggtffrrghtthgvrhhnpedvgfevffeuleegvdektdffteegvdeiieefkeetgfeuheffheelheejhfevueeijeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhhouggvpehsmhhtphhouhht >Sounds good. So what kind of interface changes should we expect? I >mean will they require updating the service definitions, run/finish >scripts, that sort of thing? (Sorry, I missed it indeed.) Nothing that drastic; service definitions will not change. They are the core of s6, and such a change would warrant a lifetime version bump, I think. No, the next release will be about a long overdue cleanup of s6-svscan and s6-svscanctl invocations: command-line options will change, and default semantics of signals received by s6-svscan will also change. The point is to remove some clutter that is either: - legacy behaviours from daemontools's svscan that have not shown they were useful - ad-hoc stuff that was added to support early iterations of running s6-svscan as pid 1, and that isn't used anymore (in part thanks to the existence of s6-linux-init 1.x) - options that experience has shown to be traps (i.e. ideas that seem good at first but really encourage bad patterns) and make the s6-svscan/ctl system less confusing to new users by only keeping a few relevant and useful configuration switches. There will also be QoL improvements to s6-svscan for people who like to nest supervision trees; also, no promises, but I may come up with some way to officially support user trees, which are a relatively common request. -- Laurent