You are combining multi-process models, which is
generally problematic. After creating a thread, you create a pipe, fork, redirect i/o and then call system, which forks again. When that second fork gets called, it seems that it is twinning the STDOUT (I assume you don't care about STDERR since you never redirect) from the main thread rather than your threaded-then-forked line of control. Why are you trying to use threads when you already have a functional code using forks and pipes? You can certain use something like the following code in place of that threading:
my $pid = fork();
if ($pid == 0) {
print "Hello!\n";
} else {
execute();
}
Another possibility is to modify your "can't modify" routine to use backticks in place of system and print the output yourself.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.