GNU bug report logs - #8408
A possible tee bug?

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Pádraig Brady <P <at> draigBrady.com>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#8408: closed (A possible tee bug?)
Date: Sat, 02 Apr 2011 00:07:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Sat, 02 Apr 2011 01:05:17 +0100
with message-id <4D96683D.5010005 <at> draigBrady.com>
and subject line Re: bug#8408: A possible tee bug?
has caused the GNU bug report #8408,
regarding A possible tee bug?
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
8408: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8408
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: George Goffe <goffe <at> google.com>
To: bug-coreutils <at> gnu.org
Subject: A possible tee bug?
Date: Fri, 1 Apr 2011 13:36:58 -0700

[Message part 3 (text/plain, inline)]

Howdy,

I have run several scripts and seen this behavior in all cases...

tee somescript | tee somescript.log 2>&1

The contents of the log is missing a lot of activity... messages and so
forth. Is it possible that there are other file descriptors being used for
these messages?

Regards,

George...

[Message part 4 (text/html, inline)]

[Message part 5 (message/rfc822, inline)]

From: Pádraig Brady <P <at> draigBrady.com>
To: George Goffe <goffe <at> google.com>
Cc: 8408-done <at> debbugs.gnu.org
Subject: Re: bug#8408: A possible tee bug?
Date: Sat, 02 Apr 2011 01:05:17 +0100

On 01/04/11 23:36, George Goffe wrote:
> 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.

somescript 2>&1 | tee log

> 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.

You could also try using `script` and then
later filtering the output through something like
http://www.pixelbeat.org/scripts/ansi2html.sh

cheers,
Pádraig

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.