topic Re: Need help about tee command... in Operating System - HP-UX

Need help about tee command...

OLIVA_1 — Wed, 04 Aug 2004 11:05:59 GMT

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,

Re: Need help about tee command...

Jeff_Traigle — Wed, 04 Aug 2004 11:16:22 GMT

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

Re: Need help about tee command...

Steven E. Protter — Wed, 04 Aug 2004 11:16:28 GMT

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

Re: Need help about tee command...

OLIVA_1 — Wed, 04 Aug 2004 11:32:34 GMT

Thank you for your help !!!

Re: Need help about tee command...

Dietmar Konermann — Wed, 04 Aug 2004 11:40:00 GMT

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.

Re: Need help about tee command...

Edgar Zapata — Mon, 16 Sep 2024 09:31:16 GMT

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