all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Carlo Zancanaro <carlo@zancanaro.id.au>
To: Dale Mellor <dale@rdmp.org>
Cc: guix-devel@gnu.org
Subject: Re: Shepherd does not recycle zombie processes
Date: Mon, 7 Nov 2016 08:21:37 +1100	[thread overview]
Message-ID: <CAFAGzb9HvrOkXAuaM=xJn6khWaV0-bX9xunceDe9FKNPkXPGMQ@mail.gmail.com> (raw)
In-Reply-To: <CAFAGzb99gGz-U-DZTaVZyk1OfMOZG_z8JxiWu3JnfnmHAYgcnQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 537 bytes --]

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" <dale@rdmp.org> 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?

[-- Attachment #2: Type: text/html, Size: 880 bytes --]

  parent reply	other threads:[~2016-11-06 21:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-05 22:22 Shepherd does not recycle zombie processes Dale Mellor
     [not found] ` <CAFAGzb_7ryGVJp1zgjYuT_czaS2o5RLMtfkEHGf9m3z=tXJ3mw@mail.gmail.com>
     [not found]   ` <CAFAGzb99gGz-U-DZTaVZyk1OfMOZG_z8JxiWu3JnfnmHAYgcnQ@mail.gmail.com>
2016-11-06 21:21     ` Carlo Zancanaro [this message]
2016-11-07  8:53       ` Ludovic Courtès
2016-11-07 11:35         ` Carlo Zancanaro
2016-11-09 14:49           ` Ludovic Courtès
2016-11-10 13:15             ` Carlo Zancanaro
2016-11-24  8:27         ` Dale Mellor
2016-11-24 13:22           ` Ludovic Courtès
2016-11-06 22:09 ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAFAGzb9HvrOkXAuaM=xJn6khWaV0-bX9xunceDe9FKNPkXPGMQ@mail.gmail.com' \
    --to=carlo@zancanaro.id.au \
    --cc=dale@rdmp.org \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.