Jose Antonio Senna wrote:
I tested TEE with commands like
DIR C: |TEE CDIR
MEM /d /f /x |TEE MAP
and it always truncates the files,that is,some lines that appear last on
screen do not appear in the file. I think this rules out the possibility
of screen output being a mix of stdout and stderr
I tested TEE with commands like
DIR C: |TEE CDIR
MEM /d /f /x |TEE MAP
and it always truncates the files,that is,some lines that appear last on
screen do not appear in the file. I think this rules out the possibility
of screen output being a mix of stdout and stderr.
Can it be that TEE make
Jim Hall wrote:
>It's possible that some of the output you see on screen was printed to
>stderr. TEE only works with output printed to stdout (that is, it only
>reads stdin.)
>stderr is often used to print warnings or error messages.
I don't think so,because the output is one continuous tran
Jose Antonio Senna wrote:
I have been using Tee to display and save output of a SMTP/POP client
named TCPMAIL. One example of command line is:
C:\!NET\TCPMAIL.EXE /q /d [EMAIL PROTECTED] |C:\UTLS\TEE .\MAIL.LST
and noticed that it truncates the file (that is,some lines - perhaps 10 - that
app
I have been using Tee to display and save output of a SMTP/POP client
named TCPMAIL. One example of command line is:
C:\!NET\TCPMAIL.EXE /q /d [EMAIL PROTECTED] |C:\UTLS\TEE .\MAIL.LST
and noticed that it truncates the file (that is,some lines - perhaps 10 - that
appear last on screen are not
