Beefy Boxes and Bandwidth Generously Provided by pair Networks
Come for the quick hacks, stay for the epiphanies.

Re: Closing STDIO Caused Pipe Not To Work

by WalkingZero (Sexton)
on Aug 27, 2007 at 04:35 UTC ( #635212=note: print w/replies, xml ) Need Help??

in reply to Closing STDIO Caused Pipe Not To Work

I will preface this by saying I have never used the PIPE command. That being said I just wanted to throw out a couple of observations. Things you may want to look into. 1) You are sending STDIN and STDOUT to devnull, what affect does this have on the bi-directional filehandles that PIPE is supposed to create?(I honestly don't know, I may be way off base with that one. If so I apologize) 2. PIPE uses IO buffering, have you tried forcing a flush of the buffer after you open the PIPE but before you write to the STDERR? (again,I'm kind of spitballing here. I hope you find it helpful, if not ignore me ;p )
  • Comment on Re: Closing STDIO Caused Pipe Not To Work

Replies are listed 'Best First'.
Re^2: Closing STDIO Caused Pipe Not To Work
by Anonymous Monk on Aug 27, 2007 at 04:43 UTC
    I think the script died when it encountered the open PIPE statement since I do not see the external program being invoked when I did I ps -aux on my linux box. However, no error is displayed anywhere even in my error_log file.

Log In?

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

How do I use this?Last hourOther CB clients
Other Users?
Others chilling in the Monastery: (5)
As of 2023-12-03 14:36 GMT
Find Nodes?
    Voting Booth?
    What's your preferred 'use VERSION' for new CPAN modules in 2023?

    Results (20 votes). Check out past polls.