You could do this: at the beginning of your script, put
(make sure it's empty first). Save the PID ($!), run your usual script with stdout redirected to the logfile (either by line or by exec 1>$logfile). At the end of your script, kill the tail (you saved the PID, didn't you?)
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 DEBIAN
logtail
LOGTAIL(8) logtail manual LOGTAIL(8)NAME
logtail - print log file lines that have not been read
SYNOPSIS
logtail [-t] -flogfile [-ooffsetfile]
DESCRIPTION
logtail reads a specified file (usually a log file) and writes to the standard output that part of it which has not been read by previous
runs of logtail. It prints the appropriate number of bytes from the end of logfile, assuming that all changes that are made to it are to
add new characters to it.
logfile must be a plain file. A symlink is not allowed.
logtail stores the information about how much of it has already been read in a separate file called offsetfile. offsetfile can be omitted.
If omitted, the file named logfile.offset in the same directory which contains logfile is used by default.
If offsetfile is not empty, the inode of logfile is checked. If the inode is changed, logtail simply prints the entire file. If the inode
is not changed but logfile is shorter than it was at the last run of logtail, it writes a warning message to the standard output.
OPTIONS -f logfile to be read after offset
-o offsetfile stores offset of previous run
-t test mode - do not change offset in offsetfile
RETURN VALUES
0 successful
65 cannot get the size of logfile
66 logfile does not exist, is not a plain file, or is not readable
73 cannot write offsetfile
AUTHOR
The original logtail was written in C by Craig H. Rowland <crowland@psionic.com>. This version of logtail is a Perl reimplementation by
Paul Slootman <paul@debian.org>. Enhanced by the Debian Logcheck Team <logcheck-devel@lists.alioth.debian.org>.
This manual was written by Oohara Yuuma <oohara@libra.interq.or.jp>.
SEE ALSO logcheck(8)Debian Fri, 19 Nov 2004 LOGTAIL(8)