pipes in Windows perlfork emulation

Discussion in 'Perl Misc' started by Henry Townsend, Apr 10, 2005.

  1. Does anyone here have any background info about the following paragraph
    which appears in "perldoc perlfork" regarding the emulation of fork()
    for Windows?

    In certain cases, the OS-level handles created by
    the pipe(), socket(), and accept() operators are
    apparently not duplicated accurately in
    pseudo-processes. This only happens in some
    situations, but where it does happen, it may result
    in deadlocks between the read and write ends of pipe
    handles, or inability to send or receive data across
    socket handles.

    I'm running into a deadlock situation involving pipes which seems much
    like that described. But before I attribute it to a Perl/Win32 bug I
    want to do some research. Unfortunately the phrasing above ("certain
    cases") is so general as to cover just about anything.

    --
    Henry Townsend
     
    Henry Townsend, Apr 10, 2005
    #1
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. piyush
    Replies:
    0
    Views:
    1,876
    piyush
    Jul 14, 2004
  2. Paul

    Windows Pipes

    Paul, Nov 25, 2003, in forum: Java
    Replies:
    1
    Views:
    1,416
  3. piyush
    Replies:
    1
    Views:
    3,223
    John Harrison
    Jul 14, 2004
  4. piyush
    Replies:
    0
    Views:
    482
    piyush
    Jul 14, 2004
  5. Henry Townsend

    Windows fork emulation (and buffering?) problem

    Henry Townsend, Apr 7, 2005, in forum: Perl Misc
    Replies:
    5
    Views:
    146
    A. Sinan Unur
    Apr 8, 2005
Loading...

Share This Page