From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/2894 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: "Serge E. Hallyn" Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: runit SIGPWR support Date: Mon, 24 Feb 2020 09:26:17 -0600 Message-ID: <20200224152617.GA28493@mail.hallyn.com> References: <1f198ed8-3682-26cd-e8d5-2efc412afde2@gmx.com> <18110531581952419@sas8-7ec005b03c91.qloud-c.yandex.net> <7003111582476686@vla3-6a5326aeb4ee.qloud-c.yandex.net> <77a6d0d5-f292-b225-e9b9-77c290394b47@gmx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="23256"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/1.9.4 (2018-02-28) Cc: supervision@list.skarnet.org To: innerspacepilot Original-X-From: supervision-return-2483-gcsg-supervision=m.gmane-mx.org@list.skarnet.org Mon Feb 24 16:26:33 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 1j6Fcv-0005tT-CR for gcsg-supervision@m.gmane-mx.org; Mon, 24 Feb 2020 16:26:33 +0100 Original-Received: (qmail 23531 invoked by uid 89); 24 Feb 2020 15:26:52 -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 23524 invoked from network); 24 Feb 2020 15:26:52 -0000 Content-Disposition: inline In-Reply-To: <77a6d0d5-f292-b225-e9b9-77c290394b47@gmx.com> Xref: news.gmane.io gmane.comp.sysutils.supervision.general:2894 Archived-At: On Mon, Feb 24, 2020 at 04:12:31PM +0300, innerspacepilot wrote: > On 24.02.2020 13:23, Laurent Bercot wrote: > > > SIGRTMIN+3 should also be caught and processed. > > > >  What piece of software sends SIGRTMIN+3 to pid 1 when you're not > > running systemd? > > > > -- > >  Laurent > > > Looking at lxc sources (src/lxc/lxccontainer.c:2084) nothing will, until > you block SIGRTMIN+3 signal. > > Even if you add SIGRTMIN+3 it will not work. Why do you say that? > Maybe we should open bug request on lxc and welcome developers from > other init systems to make an arrangement on common shutdown signal? Sure, either open an issue in github.com/lxc/lxc, or email the list (lxc-devel@lists.linuxcontainers.org) -serge