Re: POE::Wheel::Run::Win32 and Win32::Daemon

Hi, Andrew Feren wrote: > Andreas Altergott wrote: > Did you try the suggested change? Yes, I did. It did not work for me. > I tried very briefly to get Win32::Daemon working, but it didn't want to > work for me, so I can't speak to Win32::Daemon issues. That said your > original service is ex

Re: POE::Wheel::Run::Win32 and Win32::Daemon

Hi, Olivier Mengué wrote: > 2009/10/9 Andreas Altergott >> this will be especially interesting for dolman :-) > > dolmen ! Sorry for the confusion. >> This happens because POE::Wheel::Run::Win32 is using the fork() method. > > I do not know how exactly ActiveStates Perl handles the fork() me

Re: POE::Wheel::Run::Win32 and Win32::Daemon

Andreas Altergott wrote: Hi, Andrew Feren wrote: Something like the following will give you better results. my $pid; if($pid = fork()) { print(FOUT "running ($pid)\n"); wait(); } else { open(FOR, '>>', 'C:\delme-kid.txt'); thread();

Re: POE::Wheel::Run::Win32 and Win32::Daemon

In my experience Perl on Windows does not handle the (Program => \&foo) case well at all. I have had better luck with the (Program => sub { foo() }) case, but even that seems a bit iffy to me. I'm still waiting for someone who can explain why sub{ foo() } sometimes works when \&foo doesn't.

Re: Communication between a Session and TCP Client Component

2009/10/11 Dave Schwartz > Hi, > > Excuse me for spamming a long mail. Stumbled upon POE and want to use > it for my latest project. > > Don't worry. All messages on this list are usually quite long. > Is there something obviously wrong here when the user tries to give an > offset other than 0

Re: POE::Wheel::Run::Win32 and Win32::Daemon

The question in my mind: If fork() is so troublesome on Windows, do we have an alternative? For the (Program => "foo.exe") form, we can possibly avoid fork() altogether. http://rt.cpan.org/Public/Bug/Display.html?id=48715#txn-659406 includes some code that promises to work well. For the

Re: POE::Wheel::Run::Win32 and Win32::Daemon

2009/10/9 Andreas Altergott > Hi, > Hi Andreas > this will be especially interesting for dolman :-) > dolmen ! > as already described in previous emails there is a big problem when > using POE::Wheel::Run::Win32 with Win32::Daemon as a windows service. > Your service will get a termination

Re: POE::Wheel::Run::Win32 and Win32::Daemon

Hi, Andrew Feren wrote: > Something like the following will give you better results. > >my $pid; >if($pid = fork()) { > print(FOUT "running ($pid)\n"); > wait(); >} else { > open(FOR, '>>', 'C:\delme-kid.txt'); > thread(); > clo

Re: POE::Wheel::Run::Win32 and Win32::Daemon

While I have several unresolved issues with fork on Windows I think they biggest problem with your script is that the fork logic backwards. Something like the following will give you better results. my $pid; if($pid = fork()) { print(FOUT "running ($pid)\n"); wai

Re: Upcoming POE Changes

2009/10/9 Rocco Caputo > [This is a repost of > http://use.perl.org/~rcaputo/journal/39736 > ] > > I've also released Version 1.269_002 to the CPAN for developers who are > more comfortable with that. Remember: CPAN shells don't install developer > r