Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid
 
PerlMonks  

Re: Windows, threads and IPC::Open3

by ikegami (Pope)
on Nov 07, 2010 at 21:01 UTC ( #869955=note: print w/ replies, xml ) Need Help??


in reply to Windows, threads and IPC::Open3

First of all, that won't work. If either pipes fill up, the child will block and never exit. You also don't kill the child on timeout. (I'm blind!)

So let's examine what your original solution doesn't work on Windows:

  • You can only select() sockets on Windows.
  • alarm() is emulated by Perl, so it may not work in this circumstance.

Using sockets instead of pipes to communicate with the child (as demonstrated here) would solve the first problem, so all that's left would be to use select()'s timeout argument instead of alarm.

And now we'll forget everything I said because we don't want to reinvent the wheel. Just use IPC::Run.


Comment on Re: Windows, threads and IPC::Open3
Download Code
Re^2: Windows, threads and IPC::Open3
by bloonix (Scribe) on Nov 07, 2010 at 22:53 UTC
    The code example works on Windows Vista. test.pl only calls sleep(20) and the thread will be detached after 3 seconds and the process with $data{pid} is killed. :/
      If either pipes fill up, the child will block and never exit.
      If either pipes fill up, the child will block and never exit.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://869955]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others surveying the Monastery: (8)
As of 2014-12-25 08:55 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    Is guessing a good strategy for surviving in the IT business?





    Results (159 votes), past polls