09-01-2006
I mean, that i don't want to do it permanently , but from some point of execution. For example, the program and all its processes run, and when some error occures, i decide to switch to debugging mode and both view output on screen and save to log. May be durung this time new processes were created and i want to duplicate its output two. And after logging all needed data i switch back and only view output on screen.
Last edited by masha; 09-01-2006 at 03:47 PM..
Reason: second question
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
As I read the source code of unix I wonder where u_ofile(it should be stdout) link to ?
Does it link to a file structure like ordinary files? :confused: (7 Replies)
Discussion started by: jiangyanna
7 Replies
2. UNIX for Dummies Questions & Answers
Hi there
I know that this isn't the place to put a question like this i supose, but i'm geting desperated. I have searched in interbase forums and nothing helped. If anyone can help me i would apreciated.
I'm using HP-UX with a version 3 of interbase wich means i can't split the backup file into... (3 Replies)
Discussion started by: vascobrito
3 Replies
3. Solaris
Hi all,
I have a c++ program which is running fine but has some printfs which its spews on to the screen, which I need for debugging.
But, I execute this program through a java, i.e I run a java program which actually launches my c++ executable and when it does this, I see none of my printfs... (1 Reply)
Discussion started by: Naanu
1 Replies
4. UNIX for Dummies Questions & Answers
I am using a third party API to get some real time feed. When I run the command it shows the results properly:
etd@mhs-apps5009 $ mamalistenc -m lbm -tport mamaqa -S MLALERTS -s KANA wFinancialStatus
Type CTRL-C to exit.
(null).MLALERTS.KANA Type: INITIAL Status OK
wFinancialStatus |... (5 Replies)
Discussion started by: aks__
5 Replies
5. UNIX for Advanced & Expert Users
Does anyone know how I can use gzip to zip a large log file on the fly.
My simulation is currently logging a large file that I need for analysis at a later point. However the files are so huge that I may even run out of disk space. The content is mainly text so when compressed the files are... (2 Replies)
Discussion started by: mitch1710
2 Replies
6. Post Here to Contact Site Administrators and Moderators
Hi Everyone. First, I want to thank all of you for letting me participate in this great group.
I am having a bit of a problem.
After I get an email from a responder, I login to make my reply.
In the mean time I get another response by email from another member, I go to reply to them and I... (6 Replies)
Discussion started by: Ccccc
6 Replies
7. Shell Programming and Scripting
Can somebody explain to me why the diff output is not going to stderr?
Yet when I issue a diff from the command line the return code is -ne 1.
I am guessing diff always writes to stdout???
Is there away I can force the difff to write to stderr USING THE CURRENT
template. If possible, I... (5 Replies)
Discussion started by: BeefStu
5 Replies
8. UNIX for Dummies Questions & Answers
Hallo,
i have a script like:
if ;then
echo "OK"
else
echo "ERROR $2 is missing"
fi;
if ;then
touch $2
fi;
if ;then
cat $1 | grep xy > $2 (1 Reply)
Discussion started by: eightball
1 Replies
9. UNIX for Dummies Questions & Answers
Hi,
I have a program set to read in a text file, change certain characters and then print the altered version to the screen but does anyone know how to save the new version as another text file? And, if possible, how to specify the file name, and perhaps location?
Thanks! (2 Replies)
Discussion started by: PerlNutt
2 Replies
10. Linux
When unlocking a Linux server's console there's no event indicating successful logging
Is there a way I can fix this ?
I have the following in my rsyslog.conf
auth.info /var/log/secure
authpriv.info /var/log/secure (1 Reply)
Discussion started by: walterthered
1 Replies
tee(1) General Commands Manual tee(1)
NAME
tee - Displays the output of a program and copies it into a file
SYNOPSIS
tee [-ai] file...
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
tee: XCU5.0
Refer to the standards(5) reference page for more information about industry standards and associated tags.
OPTIONS
Adds the output to the end of file instead of writing over it. Ignores the SIGINT signal.
OPERANDS
Standard input is stored into, or appended to, the file specified.
[Tru64 UNIX] The tee command can accept up to 20 file arguments.
DESCRIPTION
The tee command reads standard input and writes to both standard output, and each specified file.
The tee command is useful when you wish to view program output as it is displayed, and also want to save it in a file. The tee command does
not buffer output, so you may wish to pipe the output of tee to more if more than one full screen of data is anticipated.
NOTES
If a write to any file fails, the exit status of tee will be non-zero. Writes to all other specified files may be successful, and opera-
tion will continue until standard input is exhausted.
EXIT STATUS
The following exit values are returned: Successful completion. An error occurred.
EXAMPLES
To view and save the output from a command at the same time, enter: lint program.c | tee program.lint
This displays the standard output of the command lint program.c at the terminal, and at the same time saves a copy of it in the file
program.lint. If program.lint already exists, it is deleted and replaced. To display and append to a file, enter: lint program.c |
tee -a program.lint
This displays the standard output of lint program.c at the terminal and at the same time appends a copy of it to the end of pro-
gram.lint. If the file program.lint does not exist, it is created.
ENVIRONMENT VARIABLES
The following environment variables affect the execution of tee: Provides a default value for the internationalization variables that are
unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization vari-
ables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string value,
overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of bytes
of text data as characters (for example, single-byte as opposed to multibyte characters in arguments). Determines the locale for the for-
mat and contents of diagnostic messages written to standard error. Determines the location of message catalogues for the processing of
LC_MESSAGES.
SEE ALSO
Commands: cat(1), echo(1), script(1)
Standards: standards(5)
tee(1)