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 !
- open() for IPC isn't dying ? Evgeny Goldin (aka Genie)
- Subject Prefix Eduard Grinvald
- Re: Subject Prefix Brett W. McCoy
- Re: Subject Prefix Brett W. McCoy
- Re: Subject Prefix Chas Owens
- Re: Subject Prefix Chi-Tai yang
- Re: Subject Prefix Brett W. McCoy
- Re[2]: open() for IPC isn't dying ? Evgeny Goldin (aka Genie)
- Re: Re[2]: open() for IPC isn't dying ? Nigel Wetters
- Evgeny Goldin (aka Genie)