Sorry, got the wrong end of the stick for a moment. Here's your problem (rom perldoc
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), but then your output will fail--spectacularly.
Perl can't know whether the command worked because your
command is actually running in a separate process whose
exec() might have failed. Therefore, while readers of
bogus commands return just a quick end of file, writers to
bogus command will trigger a signal they'd better be
prepared to handle.
>>> [EMAIL PROTECTED] 06/19/01 03:26pm >>>
NW> The open function lets you write or read from another program, but not both.
NW> Use the standard IPC::Open2 or IPC::Open3 modules.
But I'm only reading from it.
This e-mail and any files transmitted with it are confidential
and solely for the use of the intended recipient.
ONdigital plc, 346 Queenstown Road, London SW8 4DG. Reg No: 3302715.
