If you find your POE based daemons unresponsive after calling
Proc::Daemon::Init(), it's because the program has forked (twice) and
closed all nonstandard filehandles. POE's internal signal-handling
pipes are among the closed filehandles, and this causes some distress.
POE::Kernel->has_forked() was added a little while ago to reset
process-scoped data within POE after calling fork(). Such data
includes outstanding child PIDs and the signal pipes. Please let me
know if this doesn't fix things.
Thanks!
--
Rocco Caputo - rcap...@pobox.com
