About Proc::Daemon & POE

Rocco Caputo <[email protected]> Tue, 16 Mar 2010 02:12:10 -0400

Newsgroups	gmane.comp.lang.perl.poe
Message-ID	<[email protected]>

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 - [email protected]