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: Mon, 07 Nov 2016 09:53:57 +0100
Message-ID: <87eg2ny8ka.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>
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]:35622)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1c3fgq-000873-Ae
	for guix-devel@gnu.org; Mon, 07 Nov 2016 03:54:05 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1c3fgm-0003D1-GE
	for guix-devel@gnu.org; Mon, 07 Nov 2016 03:54:04 -0500
In-Reply-To: <CAFAGzb9HvrOkXAuaM=xJn6khWaV0-bX9xunceDe9FKNPkXPGMQ@mail.gmail.com>
	(Carlo Zancanaro's message of "Mon, 7 Nov 2016 08:21:37 +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: Dale Mellor <dale@rdmp.org>, guix-devel@gnu.org

Hi,

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

> I've had problems with Shepherd and its daemonize action. If I run
> daemonize (as the first thing when Shepherd starts) then it fails to hand=
le
> signals from child processes.

Could it be that you invoke the =E2=80=98daemonize=E2=80=99 action after re=
spawnable
processes have been started?  The manual has this caveat (info
"(shepherd) The root and unknown services"):

  =E2=80=98daemonize=E2=80=99
       Fork and go into the background.  This should be called before
       respawnable services are started, as otherwise we would not get the
       =E2=80=98SIGCHLD=E2=80=99 signals when they terminate.

HTH,
Ludo=E2=80=99.