Beefy Boxes and Bandwidth Generously Provided by pair Networks
Just another Perl shrine

Re^7: capturing stderr of echo piped to a file

by Crackers2 (Parson)
on Oct 30, 2014 at 18:31 UTC ( [id://1105665]=note: print w/replies, xml ) Need Help??

in reply to Re^6: capturing stderr of echo piped to a file
in thread capturing stderr of echo piped to a file

Okay I stand corrected in that order matters. That said, I honestly can't remember ever seeing 2>&1 not coming at the end of the command line, probably because doing so seems to indicate that it won't be captured to STDOUT as one desires.

You're entirely correct that wanting to redirect both STDOUT and STDERR is the most common case, and for that one you do indeed need the 2>&1 at the end.

However that does not appear to be what the OP wants; Unless I misread the question, he wants to capture STDERR output using the backticks, while having STDOUT going to the file. For that you need the reverse otder.

With all of the foregoing comments by both you and me in mind, I think you're first comment implies that it must come first in order to be captured.

... in order to be captured by the backticks instead of going to the file with STDOUT.

Also, it is possible that setting $| = 1; might alter the output ordering.

I think you're right about that.

  • Comment on Re^7: capturing stderr of echo piped to a file

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://1105665]
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others learning in the Monastery: (3)
As of 2024-06-20 23:10 GMT
Find Nodes?
    Voting Booth?

    No recent polls found

    erzuuli‥ 🛈The London Perl and Raku Workshop takes place on 26th Oct 2024. If your company depends on Perl, please consider sponsoring and/or attending.