On Mon, 2016-11-07 at 09:53 +0100, Ludovic Courtès wrote:
> Hi,
>
> Carlo Zancanaro 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 handle
> > signals from child processes.
>
> Could it be
Dale Mellor skribis:
> On Mon, 2016-11-07 at 09:53 +0100, Ludovic Courtès wrote:
>> Hi,
>>
>> Carlo Zancanaro 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 handle
>> > signals from c
On Wed, Nov 09 2016, Ludovic Courtès wrote
Could you run shepherd in “strace -f” and see where the SIGCHLD
signals go?
I don't really know how to read strace's output (and there's a lot
of it), but sometimes it gives a line like this:
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_KILLED,
Hi,
Carlo Zancanaro 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
Hey Ludo!
On Mon, Nov 07 2016, Ludovic Courtès wrote
Could it be that you invoke the ‘daemonize’ action after
respawnable processes have been started? The manual has this
caveat (info "(shepherd) The root and unknown services"):
‘daemonize’
Fork and go into the background. This s
Hi,
Carlo Zancanaro 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 handle
> signals from child processes.
Could it be that you invoke the ‘daemonize’ action after respawnable
processes have bee
Hi Dale,
Dale Mellor skribis:
> 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.
This may have to do with unreliable signal handling (SIGCHLD in this
case) in Guile:
https://list
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.
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?
