From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Re: Shepherd does not recycle zombie processes
Date: Wed, 09 Nov 2016 15:49:01 +0100
Message-ID: <87eg2kaeua.fsf@gnu.org>
References: <1478384577.31924.2.camel@rdmp.org>
	<CAFAGzb_7ryGVJp1zgjYuT_czaS2o5RLMtfkEHGf9m3z=tXJ3mw@mail.gmail.com>
	<CAFAGzb99gGz-U-DZTaVZyk1OfMOZG_z8JxiWu3JnfnmHAYgcnQ@mail.gmail.com>
	<CAFAGzb9HvrOkXAuaM=xJn6khWaV0-bX9xunceDe9FKNPkXPGMQ@mail.gmail.com>
	<87eg2ny8ka.fsf@gnu.org> <87a8db5xpu.fsf@zancanaro.id.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:38684)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1c4UBY-0007Dp-I6
	for guix-devel@gnu.org; Wed, 09 Nov 2016 09:49:09 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1c4UBU-0007gO-IS
	for guix-devel@gnu.org; Wed, 09 Nov 2016 09:49:08 -0500
In-Reply-To: <87a8db5xpu.fsf@zancanaro.id.au> (Carlo Zancanaro's message of
	"Mon, 07 Nov 2016 22:35:41 +1100")
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Carlo Zancanaro <carlo@zancanaro.id.au>
Cc: guix-devel@gnu.org

Hi,

Carlo Zancanaro <carlo@zancanaro.id.au> skribis:

> Yeah, I saw that note in the documentation. I used to have
>
>    (action 'shepherd 'daemonize)
>
> as the first line in ~/.config/shepherd/init.scm. Is there some other
> way that I was supposed to do that?

No, I think that should work.

> With that line in place, Shepherd will leave behind a process every
> time I stop/start a service.
>
> I have attached an example init.scm that does this for me. If I start:=20
>
>    shepherd -c init.scm
>
> and then run:
>
>    herd stop sleep
>    herd start sleep
>    herd stop sleep
>    herd start sleep
>    herd stop sleep
>
> then I will have three zombie sleep processes underneath my Shepherd
> process. (If the service were respawnable then it also would fail to
> restart the service.)

Could you run shepherd in =E2=80=9Cstrace -f=E2=80=9D and see where the SIG=
CHLD signals
go?

Thanks,
Ludo=E2=80=99.