First things first: on my WS the behavior is identical with or without eval {} around the call to _run, and every 10 seconds a new process comes to life.

That seems actually OK, as 'blubb' doesn't produce any output and so the forked child process loops forever in 
   while (my $line = <$rdr>) {
     [...]
   }

[download]
Update: In the meantime, the parent process does it's work and forks a new command every 10 seconds.
As almut has shown in his her answer, it's a child that forks a child that forks a child... and each new parent waits indefinitely.

If I replace 'blubb' with 'echo blubb', things seem to work as I suppose you want them to.


Krambambuli
---

In reply to Re: Problems with IPC::Open3 by Krambambuli
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.