Re^8: capturing output of system call inside a thread

[BrowserUk]

In which case I want to capture STDOUT and STDERR of each worker "process".

And there is the source of my question: Why are you quoting "process"?

Either this is

1. a real separate process;

   In which case you need to 'capture' the output from STDOUT and STDERR.

2. Or it is just perl code running in a thread; and using the term 'process' is just misleading.

   In this case you don't need to 'capture' the output; you simply need to direct it to where you want it to go.

   Ie. If you are going to call a subroutine that normally writes to stdout and stderr; and you want that output to end up in a file of your choosing, then point stdout and stderr to that file before you call the subroutine:

   sub worker {
       local( *STDOUT, *STDERR );
       open STDOUT, '>', 'my.log' or die $!;
       open STDERR, '>&STDOUT' or die $!;
       unmodifiable(); ## call the code that produces the output; it'll e
   +nd up in my.log
       ## the effects of the redirection get cleaned up automatically whe
   +n the worker ends.
   }
   

[that_guy]

Thanks for the answer. Your solution doesn't work. Output of the program run by system call still is being printed to the screen and not to the log file. Perhaps you should have spend less time on being a pedantic prick and spend 5 seconds on actually running the code you provided.

[BrowserUk]

. Your solution doesn't work. Output of the program run by system call still is being printed to the screen and not to the log file.

It would. The solution I posted (as I clearly identified in the post), will only work for perl code running in the current process.

You need the second part for external processes; but we never got that far.

Its actually very trivial; but now you'll have to make that discovery for yourself won't you.

(That's the trouble with shills; they so quickly self identify.)