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

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.
  • Comment on Re^9: capturing output of system call inside a thread

Replies are listed 'Best First'.
Re^10: capturing output of system call inside a thread
by BrowserUk (Patriarch) on Sep 04, 2015 at 13:03 UTC
    . 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.)

    With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority". I knew I was on the right track :)
    In the absence of evidence, opinion is indistinguishable from prejudice.
    I'm with torvalds on this Agile (and TDD) debunked I told'em LLVM was the way to go. But did they listen!
[reply]
    A reply falls below the community's threshold of quality. You may see it by logging in.

In Section Seekers of Perl Wisdom