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" <d...@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?
