You can google for "closing stdout apache" for a bunch of discussion on how to do it, But basically the code is 
$| = 1;    # need either this or to explicitly flush stdout, etc. 
# before forking 
print "Content-type: text/plain\n\n";
print "Going to start the fork now\n";
if ( !defined(my $pid = fork())) {
print STDERR "fork error\n";
exit(1);
} elsif ($pid == 0) {
# child 
close(STDOUT);close(STDIN);close(STDERR);
exec('./fork-long-process-test-process');     # lengthy processing 
} else {
# parent 
print "forked child \$pid= $pid\n";
exit 0;
}

[download]

When I saw the node title, the first thing that poped up in my mind was a "big red warning flag" not to use exec in threads. Why? Because the exec will take over the process completely and destroy all other threads that were running under the parent, including the parent. You can "fork-and-exec" from a thread with no problem.

The way you are describing your code, I don't see why you are even using threads to begin with? But you are seemingly on windows, and I'm clueless on how Windows does things. I mention it, because it may cause some sort of "weird" problem where you can't close STDOUT because the parent was destroyed.

I'm not really a human, but I play one on earth. flash japh

In reply to Re: Thread and exec by zentara
in thread Thread and exec by farmerajf

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.