On 05/21/2014 02:45 PM, Helmut Grohne wrote:
On Wed, May 21, 2014 at 02:34:45PM -0700, Ethan Furman wrote:
The second thing you want is for continued set up to happen in Child after
Child is spawned... oh, wait -- I think I understand -- you want Parent to
hang around and wait for the result of the continued set up in Child, so it
can report any errors encountered... have I understood?
Yeah, if there was no need to do setup in the child, the whole problem
would go away. Just setup first and then daemonize. Unfortunately some
things must be set up in the child, but with the current implementation
the child can no longer signal any failures back to the user. All it can
do is fail silently. Bad.
I feel your pain! :) I just had the same experience with PID files, which likewise must be done in the child but
failures don't make it back to the parent (because the parent is gone).
Ben, how amenable are you to API change?
--
~Ethan~
_______________________________________________
python-daemon-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-daemon-devel
