From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/2884 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: Thu, 20 Feb 2020 14:39:09 -0600 Message-ID: <20200220203909.GA8710@mail.hallyn.com> 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; charset=us-ascii Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="18150"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/1.9.4 (2018-02-28) Cc: supervision To: Laurent Bercot Original-X-From: supervision-return-2473-gcsg-supervision=m.gmane-mx.org@list.skarnet.org Thu Feb 20 21:39:23 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 1j4sbT-0004Ws-C8 for gcsg-supervision@m.gmane-mx.org; Thu, 20 Feb 2020 21:39:23 +0100 Original-Received: (qmail 19158 invoked by uid 89); 20 Feb 2020 20:39:41 -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 19146 invoked from network); 20 Feb 2020 20:39:41 -0000 Content-Disposition: inline In-Reply-To: Xref: news.gmane.io gmane.comp.sysutils.supervision.general:2884 Archived-At: On Tue, Feb 18, 2020 at 09:39:14AM +0000, Laurent Bercot wrote: > In the former case, lxd *emulates* a kernel, and is supposed to adapt > to every kind of init that runs in a container, so it should follow > existing conventions and be able to adapt to every init. And that's > exactly why the lxc.signal.stop configuration switch exists! Yes, it is. And for the most part, container creation templates should know what sort of distro, and hence init, they are setting up, so they can add the right lxc.signal.stop. But it *is* too bad that there is no way really to query "hey, for this init that's running in this container, what *should* I send it?" I suspect that's where some users get annoyed. If you're creating and destroying a lot containers with a lot if different distros, I can see where having to guess this for yourself can be a bit of a blocker. So since you can't query, a convention would be nice. But that ship too has sailed. -serge