Thanks for the answers.

I want to keep it as simple as possible, also I would prefer it to have "real-time" update, not waiting for a buffer to fill up. This is my fileevent function:

sub fill_text_widget {
my $block = shift;
my $numb = shift;
my $widget = $Reg_r{$block}{$numb}{'Txt'};
my $out_rep = $Reg_r{$block}{$numb}{'OutP'};
if (eof($out_rep))
{
    $widget->fileevent($out_rep,"readable", undef);
    close $Reg_r{$block}{$numb}{'OutP'};
    print "Got EOF\n" if ($DBG);
    $Reg_r{$block}{$numb}{'IsRun'} =0;
    &AddReRun($block, $numb);
    return;
} 
$_ = <$out_rep>;
$widget->insert('end', $_);
$widget->yview('end');
}

[download]

The annoying part, is that the gui keeps working fine after launching the open as if in real background, the gui is completely functional. Only when I invoke an additional process, let's say an xterm, the gui suddenly gets blocked, although both jobs are running. The gui will be free only when the initial open is done

regrading the option to use FCNTL, can you elaborate on it? I tried using it, didnt made a difference, but I think I didn't do it properly. Can I keep using fileevent or do I have to move to read?

In reply to Re: Second background process is pausing the gui by Anonymous Monk
in thread Second background process is pausing the gui by Ohad

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.