looks to me like it isn't an issue of killing the process, but instead a matter of using the <FH> style of reading that basically blocks, waiting for more input from the program. Could you elaborate a bit on what kind of program it is and what kind of data it is feeding the script? If you know for example that it will always generate x bytes or y lines of information, perhaps it would be better to perform a non-buffered read using sysread on DUMP and then closing the filehandle(assuming the program you're using won't choke on that kind of thing).

Alternatively, is there any way to convince the program you're calling to write the information to ie a textfile, which your script can then process in a more relaxed fashion?

Remember rule one...

In reply to Re: more problems running a program that hogs the termnial by Forsaken
in thread more problems running a program that hogs the termnial by GaijinPunch

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.