Greetings, esteemed monks!

Thanks for the tips, all. I will have to go in and read the source for open3(). It turns out that the first approach (using sysreads) causes some processes not to finish, whereas I was not getting problems with the $line= scalar <$fh> thing. I only started messing with it because we have a particularly lengthy script, and the output wasn't showing up in the log even though the script had started. That may have had something to do with turning autoflush on in the called script though.

_________________________________________________________________________________
Without me, it's just aweso

In reply to Re: Best practice for sychronous output handling using open3()? by OfficeLinebacker
in thread Best practice for sychronous output handling using open3()? by OfficeLinebacker

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.