in reply to IPC::Open3 & closed STDOUT

You haven't listed _runReadWrite, so how can we comment on modifying its inner workings? For that matter you say 'it fails'. How??? Does it die, hang, segfault?

Replies are listed 'Best First'.
Re: Re: IPC::Open3 & closed STDOUT
by Anonymous Monk on Nov 18, 2003 at 14:15 UTC
    Hi ptkdb, here is the full sub listing...
    sub _run_ReadWrite { my ($invocant, $cmd, $input) = @_; # declare needed variables and connect to process local (*CHILD_IN, *CHILD_OUT, *CHILD_ERR); my ($childpid, @outlines, @errlines); $childpid = open3(*CHILD_IN, *CHILD_OUT, *CHILD_ERR, $cmd); # feed input to process, then close input print CHILD_IN $input; close (CHILD_IN); # save output and errors, close those channels and the process chomp(@outlines = <CHILD_OUT>); close (CHILD_OUT); chomp(@errlines = <CHILD_ERR>); close (CHILD_ERR); waitpid($childpid, 0); # return the result of the call return { OUTPUT => \@outlines , ERRORS => \@errlines }; }
    Now like I said, calls to this sub return exactly what I expect, as long as I pass a valid $cmd and $input.

    The problem is when a call to this function is made from a script that has, for some reason, closed STDOUT, the @outlines array ends out empty. The process doesn't hang or fail, in fact everything works fine, its just that the launched process' output "gets lost" somewhere. I want to be able to catch it !

    Is that clearer ?

    Thanks for your help
      Next Question: What '$cmd' is not giving you output? Does it work for simple things like 'ls' but not for something else?