I am not sure about your question.
If the problem is buffering be sure you have set them to flush:
use IO::Handle; $F = new IO::Handle; $F->autoflush(1);
If what you want is to filter the output then create a filter by forking again like in this example
$ cat -n openself 1 #!/usr/local/bin/perl -w 2 use strict; 3 use utf8; 4 binmode(STDOUT, ':utf8'); 5 binmode(STDIN, ':utf8'); 6 7 print "Father: $$\n"; 8 9 my $pid = open(STDOUT, "|-"); 10 die "cannot fork: $!" unless defined $pid; 11 12 # Child filters father's output 13 filterstdout() unless $pid; 14 15 # Father 16 print " <- This is the PID of the child\n"; 17 while (<>) { 18 print 19 } 20 21 sub filterstdout { 22 while (<STDIN>) { 23 tr/áéíóúñ€/aeioun$/; 24 print "$$: $_"; 25 } 26 exit; 27 }

Hope it helps

Casiano


In reply to Re: a way to handle the multiple processes output by casiano
in thread a way to handle the multiple processes output by scarus

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.