2009/10/13 Andrew Feren acfe...@yahoo.com
I'm not really sure, but I'd guess that the Daemon module isn't
copying/cloning something that it should. As a result
Win32::Daemon::StopService(); is getting called unexpectedly in a DESTROY or
END block when the child exits.
That is probably the
On 15-Oct-2009 flw wrote:
Even if there is no defined $@, it also need to alarm(0).
Maybe I'm being dense, but I don't see how the eval {} could exit with an alarm
still set but $@ not set. Or is there some magic to alarm() and SIG{ALRM} that
I'm unaware of.
Also, could you write a test case
What is the best way to enable TCP keepalive on a
POE::Component::Client::TCP session?
I am using POE for home automation and I have connections which are
often idle for hours, or only get traffic in the receive direction. In
these cases there is no indication that the connection has
Hi,
Andrew Feren wrote:
I removed the calls to exit() and the service started working as
expected. Calling exit() from the child resulting from perl's pseudo
fork is supposed to work (and often does). Unfortunately it has been my
experience that sometimes the results are a catastrophic
Andreas Altergott wrote:
Hi,
Andrew Feren wrote:
I removed the calls to exit() and the service started working as
expected. Calling exit() from the child resulting from perl's pseudo
fork is supposed to work (and often does). Unfortunately it has been my
experience that sometimes the
