If you like to log the details to the log file as well as display it in o/p, then you should use tee command. If you just need to redirect it to a file, then use the >> redirect operator.
If you think it is too cumbersome to type it in every line of the script, then open vi and then take it to the command mode and then
the above command should be able to put the tee for you.
cheers,
Devaraj Takhellambam
devtakh
I can do this, but if someone views my code it looks like so many tee.
I dont want to append tee when i am using sed or awk for processing; only when i am echoing.
i thought there might be a way where i can take output of each function and output it on screen as well as in log file, without using tee at each line.
Greetings to everybody. I would like to know if I can use the pipe and command tee to read from edited file and to write to him e.g. "sed '{s_A_B_}' file | tee file". :confused: I know it doesn't work with > but I don't know anything about it with tee. Thank you for your help. :) (1 Reply)
hello
how to append the hostname to each line of a file that is tee'd
for example:
tail -f file1 | tee file2
Iwant file2 to have the same new lines of file1 but with the hostname at the end or the beginning of each line.
btw, is there more proper method than: tail -f file1 | tee... (1 Reply)
Someone recently advised me to use the tee command to write to standard out.
Why would you pipe your commands to
tee -a <filename>
rather than just using
>> <filename>
?
For example:
date|tee -a myfile
seems to be the same as
date >> myfile
Is there a benefit to... (5 Replies)
I have been using the command tee to store the output to a file and also write on the terminal. However I would need to put the program in the background although I would still need to see the file being updated like it was doing when using tee.
Any suggestions on how to look at the log file... (3 Replies)
script1:
#!/bin/ksh
more test.txt
script2: calling the script1
#!/bin/ksh
/tmp/script1.sh 2>&1 | tee tee.log
where test.txt contains ~1200 lines.
When I execute the script2 the more command does not print pagewise it goes to the end of the line, when I remove the tee command it... (4 Replies)
Greetings!
My apologies if this has been answered elsewhere before. What I have is a function (as below) set up to append to either an error log or info log based upon input.
myLOGGER ()
{
if ]; then
logfile=$elog
lastERROR="$1" #used elsewhere in my script
else... (2 Replies)
In the current directory , I have seven files .
But when I use the following command , it lists eight files ( 7 files + file_list.xtx)
ls -1 | tee file_list.xtx | while read line; do echo $line ; done
Does the tee command create the file_list.xtx file first and then executes the ls -1... (1 Reply)
Hi Everybody! First post! Totally noobie.
I'm using the terminal to read a poorly formatted book.
The text file contains, in the middle of paragraphs, hyphenation to split words that are supposed to be on multiple pages. It looks ve -- ry much like this.
I was hoping to use grep -v " -- "... (5 Replies)
I'm on Ubuntu 14.04 and I manually updated my coreutils so that "tee" is now on version 8.27
I was running a script using bash where there is some write to pipe error at some point causing the tee command to exit abruptly while the script continues to run. The newer version of tee seems to prevent... (2 Replies)
Discussion started by: stompadon
2 Replies
LEARN ABOUT XFREE86
tee
TEE(1) User Commands TEE(1)NAME
tee - read from standard input and write to standard output and files
SYNOPSIS
tee [OPTION]... [FILE]...
DESCRIPTION
Copy standard input to each FILE, and also to standard output.
-a, --append
append to the given FILEs, do not overwrite
-i, --ignore-interrupts
ignore interrupt signals
-p diagnose errors writing to non pipes
--output-error[=MODE]
set behavior on write error. See MODE below
--help display this help and exit
--version
output version information and exit
MODE determines behavior with write errors on the outputs:
'warn' diagnose errors writing to any output
'warn-nopipe'
diagnose errors writing to any output not a pipe
'exit' exit on error writing to any output
'exit-nopipe'
exit on error writing to any output not a pipe
The default MODE for the -p option is 'warn-nopipe'. The default operation when --output-error is not specified, is to exit immediately on
error writing to a pipe, and diagnose errors writing to non pipe outputs.
AUTHOR
Written by Mike Parker, Richard M. Stallman, and David MacKenzie.
REPORTING BUGS
GNU coreutils online help: <http://www.gnu.org/software/coreutils/>
Report tee translation bugs to <http://translationproject.org/team/>
COPYRIGHT
Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.
SEE ALSO
Full documentation at: <http://www.gnu.org/software/coreutils/tee>
or available locally via: info '(coreutils) tee invocation'
GNU coreutils 8.28 January 2018 TEE(1)