From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carlo Zancanaro Subject: Re: Shepherd does not recycle zombie processes Date: Mon, 7 Nov 2016 08:21:37 +1100 Message-ID: References: <1478384577.31924.2.camel@rdmp.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=94eb2c03d3e01d1baa0540a87ee8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56728) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c3Usm-0000Bg-FW for guix-devel@gnu.org; Sun, 06 Nov 2016 16:21:41 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c3Usl-0001J4-Dz for guix-devel@gnu.org; Sun, 06 Nov 2016 16:21:40 -0500 Received: from mail-it0-x22f.google.com ([2607:f8b0:4001:c0b::22f]:38117) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1c3Usl-0001GJ-8T for guix-devel@gnu.org; Sun, 06 Nov 2016 16:21:39 -0500 Received: by mail-it0-x22f.google.com with SMTP id q124so83744243itd.1 for ; Sun, 06 Nov 2016 13:21:38 -0800 (PST) In-Reply-To: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Dale Mellor Cc: guix-devel@gnu.org --94eb2c03d3e01d1baa0540a87ee8 Content-Type: text/plain; charset=UTF-8 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 handle signals from child processes. I've only been running without the daemonize call for a day or so, but it seems to properly handle the child processes now. On 06/11/2016 9:52 am, "Dale Mellor" wrote: I'm running shepherd stand-alone in a Debian system. But I am seeing zombie processes which have been kicked off by shepherd, and they do not get re-spawned. Any suggestions? --94eb2c03d3e01d1baa0540a87ee8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

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

I've only been running without the daemonize call for a = day or so, but it seems to properly handle the child processes now.


On 06/11/2016 9:5= 2 am, "Dale Mellor" <dale@rdm= p.org> wrote:
I'= ;m running shepherd stand-alone in a Debian system.=C2=A0 But I am seeing zombie processes which have been kicked off by shepherd, and they do not get re-spawned.

Any suggestions?




--94eb2c03d3e01d1baa0540a87ee8--