Thanks for the suggestions. My main goal is to just log the output, grep different strings while the called program is running, highlight errors and other stuff. But in some situations I have to provide input. I thought that I could blame open3 because I thought that the called program whould inherit the stdout-filehandle and its properties, so I wrote a wrapper-script 

use IO::Handle;
STDOUT->autoflush(1);
exec ./program_to_launch

[download]

And then I called the wrapperscript with open3. But it doesnt seem to work. I think I haven't really understand where the buffering actually takes place. I will now take a look at IO::Pty.

-Stefan

In reply to Re^2: IPC::Open3 buffering and autoflush by morpheus
in thread IPC::Open3 buffering and autoflush by morpheus

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.