Howdy,
I have run several scripts and seen this behavior in all cases...
tee somescript | tee somescript.log 21
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...
George Goffe writes:
Howdy,
I have run several scripts and seen this behavior in all cases...
tee somescript | tee somescript.log 21
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
Alan,
Thank you for your help.
Sorry to bother you with such a trivial problem. I'm still learning unix
after all these years. Sigh.
Have a GREAT weekend and, again, Thanks.
George...
On Fri, Apr 1, 2011 at 3:41 PM, Alan Curry pacman...@kosh.dhis.org wrote:
George Goffe writes:
Alan,
George Goffe writes:
Alan,
Oops. I goofed... My apologies.
The example would be this somescript | tee somescript.log 21.
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
Alan,
Oops. I goofed... My apologies.
The example would be this somescript | tee somescript.log 21.
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
On 01/04/11 23:36, George Goffe wrote:
Alan,
Oops. I goofed... My apologies.
The example would be this somescript | tee somescript.log 21.
The intent is to capture all the output (stdout and stderr) from
somescript. somescript runs several commands that may or may not utilize
other
