From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/2887 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Jeff Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: runit SIGPWR support Date: Sun, 23 Feb 2020 18:31:51 +0100 Message-ID: <6637411582479111@sas8-ed615920eca2.qloud-c.yandex.net> References: <20200131043919.GF12551@cathexis.xen.prgmr.com> <20200214131544.tcvmh7tqu4hu2gul@caspervector> <1f198ed8-3682-26cd-e8d5-2efc412afde2@gmx.com> <18110531581952419@sas8-7ec005b03c91.qloud-c.yandex.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="87060"; mail-complaints-to="usenet@ciao.gmane.io" To: superstition Original-X-From: supervision-return-2476-gcsg-supervision=m.gmane-mx.org@list.skarnet.org Sun Feb 23 18:32:05 2020 Return-path: Envelope-to: gcsg-supervision@m.gmane-mx.org Original-Received: from alyss.skarnet.org ([95.142.172.232]) by ciao.gmane.io with smtp (Exim 4.92) (envelope-from ) id 1j5v6q-000MPD-Ma for gcsg-supervision@m.gmane-mx.org; Sun, 23 Feb 2020 18:32:04 +0100 Original-Received: (qmail 30826 invoked by uid 89); 23 Feb 2020 17:32:24 -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 30819 invoked from network); 23 Feb 2020 17:32:24 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1582479111; bh=Vkn1P6+VBaKDE2OIrzbjas7S/DvF0wL/VJ1qieWIVYA=; h=References:Date:Message-Id:Subject:In-Reply-To:To:From; b=J+WZma7rTBRBONquoHaeC4ceeIEHcwufCpQHkp7KuUgdatVBnCP981axWJjr5Qx51 NNncHW9+EDrIEzHKr4ZXm2d3EniAgrVi3FqjZk3PYh6/wnGnMtm3mxNse3S7Dj8qAu c0nXcCsUGoANsgTno/p4aJrVmDucHbvNfe4MTyts= Authentication-Results: mxback20j.mail.yandex.net; dkim=pass header.i=@yandex.com In-Reply-To: X-Mailer: Yamail [ http://yandex.ru ] 5.0 Xref: news.gmane.io gmane.comp.sysutils.supervision.general:2887 Archived-At: 18.02.2020, 10:39, "Laurent Bercot" : > you're telling me that s6-svscan needs to understand SIGPWR in case the > kernel wants to signal a power failure, you actually have a good point, > and yes, I should implement SIGPWR support when this signal exists. BTW: have you ever used s6 as process #1 on any other platform than Linux ? i bet you have not even tried to do so on any of the BSDs. so why are you sticking to all this "POSIX-correctness" ? adding a few lines of code to support a specific platform (linux or any other unix) looks not like a big problem to me. sticking to POSIX features in the default case is a good way to achieve portability, that's right. but avoiding platform specific advantages at all costs seems pretty strange to me. solaris, AIX and even OS X are all POSIX platforms, hence it would be interesting to see if s6 will work out of the box there (as process #1; handling SIGPWR may be a requirement here). i am sure it will since unlike systemd it is portable. those platforms cannot be "POSIX-correct" if not. hence their kernels should be made "POSIX-correct" to run the "POSIX-correct" s6 unchanged as process #1. so who has to adapt, s6 or those kernels ?