On a related note, documentation says that supervisord relies on SIGCHLD to
be notified of a monitored process termination:
http://supervisord.org/subprocess.html
However, in the code I see that SIGCHLD is swallowed with a mere log
message, while the actual mechanism seems to rely on a file
Hello,
I have an error-handling question about supervisord.
In case if supervisord crashes or exits abnormally, and then it is
restarted, would the new instance of supervisord be able to harvest the
process list and to continue monitoring processes started by its
predecessor?
Or would it try to
