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.

In reply to Re: Problems with IPC::Open3 by almut
in thread Problems with IPC::Open3 by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.