GNU bug report logs -
#8408
A possible tee bug?
Previous Next
Reported by: George Goffe <goffe <at> google.com>
Date: Fri, 1 Apr 2011 20:41:02 UTC
Severity: normal
Done: Pádraig Brady <P <at> draigBrady.com>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
George Goffe writes:
> Alan,
>
> Oops. I goofed... My apologies.
>
> The example would be this "somescript | tee somescript.log 2>&1".
>
> The intent is to capture all the output (stdout and stderr) from
> "somescript". "somescript" runs several commands that may or may not utilize
> other FDs. I was hoping to get a better output than what you might get from
> the script command which records all the messages + a ton of other things
> like escapes which are a pain to eliminate.
>
> Does this make better sense?
Well, you still have the 2>&1 in the wrong place. If you want it to affect
the stderr of the command to the left of the pipe, you have to put it to the
left of the pipe.
This bug report was last modified 14 years and 58 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.