Need help about tee command...

[OLIVA_1]

Hello,

I would like trace all command I type in a log file.
For this I use: ksh | tee -a /tmp/log_file and I type my command "ls", "bdf", "uname -a" etc...

When I read /tmp/log_file I can see the command result but not the command typed... someone can help me ?

I would like a log file where I could see my command and its result.

Thanks,

[Jeff_Traigle · Accepted solution]

Check out the man page for script. It will make a transcript of your entire session until you exit it.

[Steven E. Protter]

I generally use tee to split a copy of the output of individual commands to a log file

bdf | tee $logfile

for example.

Your methdology is interesing but unfamiliar to me. I wonder if its a supported use.

SEP

[OLIVA_1]

Thank you for your help !!!

[Dietmar Konermann]

Of course Oliva's use of tee(1) is supported... and the supporter's answer is "works as designed". :-)

The tee command duplicates its stdin stream and end sends one copy to stdout and the other one to a file.

With "ksh | tee -a /tmp/log_file" the stdout of ksh is piped to tee's stdin. So tee copies ksh's stdout to the file. But what you are typing at the prompt is ksh's stdin... not the stdout.

Use the script(1) command instead, as already suggested.

Best regards...
Dietmar.

[Edgar Zapata]

is there a way you can make it with the
.sh_history and/or .bash_history files?