[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-bug-tracker] bug#8408: closed (A possible tee bug?)

From: GNU bug Tracking System
Subject: [Emacs-bug-tracker] bug#8408: closed (A possible tee bug?)
Date: Sat, 02 Apr 2011 00:07:02 +0000

Your message dated Sat, 02 Apr 2011 01:05:17 +0100
with message-id <address@hidden>
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

8408: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8408
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: A possible tee bug? Date: Fri, 1 Apr 2011 13:36:58 -0700 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?



--- End Message ---
--- Begin Message --- Subject: Re: bug#8408: A possible tee bug? Date: Sat, 02 Apr 2011 01:05:17 +0100 User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20100227 Thunderbird/3.0.3
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


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]