in reply to Problems with IPC::Open3

I'm assuming 'blubb' doesn't exist... If so, when you call open3() not being wrapped in an eval, the forked child dies with "open3: exec of blubb failed at ./720878.pl line 23", and you're reading that message via <$rdr> (because you passed in an undefined $err handle, the child's stdout and stderr are redirected to the same handle).

However, when you call open3() wrapped in an eval, it doesn't die with the above message, and thus your <$rdr> will wait forever. What makes things complicated is that - as the exec of blubb failed - the child lives on as a forked copy of the parent, which will start the next iteration (and another child process) after 10 seconds...

Moral of the story: don't wrap IPC::Open3::open3() in eval to catch exec errors.

Replies are listed 'Best First'.
Re^2: Problems with IPC::Open3
by Anonymous Monk on Nov 01, 2008 at 21:38 UTC
    I think thats a strong bug! The child must be exited in any case after exec().

      I agree... though, as it looks, the problem has 'already' been fixed in the version that comes with 5.10.0.

        Yes, but how can I fix it with 5.8.8?
      But how can I update IPC::Open3 on my perl 5.8.8? I don't like to install perl 5.10.0 on my production machines.

        It doesn't seem to be in a distribution separate from Perl, so you will have to download the source and copy it over the existing Open3.pm file (after making a backup of the old file). Hopefully you won't encounter other required prerequisites that your current Perl doesn't match (see the "backup" part in the sentence before this one). Alternatively you can hold out until Perl 5.8.9 gets released, which likely will include the latest IPC::Open3.