From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/2477 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: "Laurent Bercot" Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: s6 bites noob Date: Fri, 01 Feb 2019 00:36:07 +0000 Message-ID: References: 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="235501"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: eM_Client/7.2.33939.0 To: supervision@list.skarnet.org Original-X-From: supervision-return-2067-gcsg-supervision=m.gmane.org@list.skarnet.org Fri Feb 01 01:36:09 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 1gpMoT-000z8m-Nm for gcsg-supervision@m.gmane.org; Fri, 01 Feb 2019 01:36:09 +0100 Original-Received: (qmail 26398 invoked by uid 89); 1 Feb 2019 00:36:34 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm Original-Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 26391 invoked from network); 1 Feb 2019 00:36:34 -0000 In-Reply-To: X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: 0 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedtledrjeejgddvfecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfpfgfogfftkfevteeunffgpdfqfgfvnecuuegrihhlohhuthemuceftddtnecunecujfgurhephffvufffkfgjfhhrfgggtgfgsehtqhertddtreejnecuhfhrohhmpedfnfgruhhrvghnthcuuegvrhgtohhtfdcuoehskhgrqdhsuhhpvghrvhhishhiohhnsehskhgrrhhnvghtrdhorhhgqeenucfrrghrrghmpehmohguvgepshhmthhpohhuthenucevlhhushhtvghrufhiiigvpedt Xref: news.gmane.org gmane.comp.sysutils.supervision.general:2477 Archived-At: >>s6-svc -wu -u serv/foo/ will start it, but never exits. Likewise, s6-svc= -wd -d serv/foo/ will stop it, but never exits. > >Now that is probably due to your setup, because yours is the only >report I have of it not working. Update: just tonight I received another report of the exact same symptoms, so I investigated, and indeed it's a bug I had introduced a few commits ago. Sorry about that! It is now fixed in the current s6 git head, so if you git pull and rebuild s6, everything should now work flawlessly. (No need to rebuild s6-rc.) -- Laurent