in reply to Re: open ($FH,"<named pipe") blocking
in thread open ($FH,"<named pipe") blocking

I think you misunderstood what they're asking. They're trying to open a named pipe, which is a special pipe which lives in the filesystem. When you try and open it the open(2) system call underneath will block if there's no writer on the other end.

They need to look at the O_NONBLOCK flag for sysopen rather than using open.

Update: Excepting of course that that will just make the sysopen fail with a return code of EAGAIN (I believe). That's just the way named pipes work; the call blocks until there's something on the other end.

Replies are listed 'Best First'.
Re^3: open ($FH,"<named pipe") blocking
by gnu@perl (Pilgrim) on May 12, 2005 at 18:36 UTC
    You nailed it. I knew it was something simple, but it has been soooooo long since I had to use pipe for anything I forgot about sysopen. Thanks.