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.
This works perfectly, and does what I expect it to do. Whatever message I put in quotes is passed to the function and appended to the appropriate file.
My question is in whether I can use the command tee to output the same message to the screen and my function?
I know that I can do this:
What I'd like to do is something like the below, but I haven't found a way to do so.
I know that I can use tee within my function, however not everything I'm sending to the logs needs to be displayed as well. I suspect that I would just have to add another if statement and pass an additional argument to myLOGGER.
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)
Hi,
I have a script where i want to log in details to the standard output as well as log file so that its easy for tracing purposes.
I have used the "tee"command.
The problem with this is my scripts lines are getting longer as for each line i have
#!/bin/ksh
echo "hello world" |... (4 Replies)
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)
I have 7 functions those need to be executed as command line inputs, I tried with below code it’s not executing function. If I run the ./script 2 then fun2 should execute , how to initiate that function I tried case and if else also, how to initiate function from command line
if
then... (8 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)
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 SUSE
logsave
LOGSAVE(8) System Manager's Manual LOGSAVE(8)NAME
logsave - save the output of a command in a logfile
SYNOPSIS
logsave [ -asv ] logfile cmd_prog [ ... ]
DESCRIPTION
The logsave program will execute cmd_prog with the specified argument(s), and save a copy of its output to logfile. If the containing
directory for logfile does not exist, logsave will accumulate the output in memory until it can be written out. A copy of the output will
also be written to standard output.
If cmd_prog is a single hyphen ('-'), then instead of executing a program, logsave will take its input from standard input and save it in
logfile
logsave is useful for saving the output of initial boot scripts until the /var partition is mounted, so the output can be written to
/var/log.
OPTIONS -a This option will cause the output to be appended to logfile, instead of replacing its current contents.
-s This option will cause logsave to skip writing to the log file text which is bracketed with a control-A (ASCII 001 or Start of
Header) and control-B (ASCII 002 or Start of Text). This allows progress bar information to be visible to the user on the console,
while not being written to the log file.
-v This option will make logsave to be more verbose in its output to the user.
AUTHOR
Theodore Ts'o (tytso@mit.edu)
SEE ALSO fsck(8)E2fsprogs version 1.41.11 March 2010 LOGSAVE(8)