perlipc :

> If you're *writing* to a pipe, you should also trap SIGPIPE
> Otherwise, think of what happens when you start up a pipe to a command
> that doesn't exist: the open() will in all likelihood succeed (it only
> reflects the fork()'s  success)

Hmm .. Although perlipc is talking about *writing* to pipe and I'm only
*reading* from it - it still looks like the same problem. I'll give it a try ..
Thank you !

Reply via email to