03-27-2009
Why didnt you use | tee <outfile.file>?
10 More Discussions You Might Find Interesting
1. AIX
Hi,
I am creating a test package and putting echo statements in the custom scripts (preinstall, postinstall, preremove, etc).
Here is the template file
Pre-installation Script: <pre-install script>
Post-installation Script: <post-install script>
These are getting called.
How do i... (4 Replies)
Discussion started by: vibhor_agarwali
4 Replies
2. AIX
I have created a .bff package for an app to tbe installed on AIX servers across regions. I am pretty new to the AIX mode of packaging using mkinstallp but I have been able to get the same done. I installed the same on the server in which i created the package and the application was deployed... (9 Replies)
Discussion started by: jobbyjoseph
9 Replies
3. Shell Programming and Scripting
Hi,
I have a "package" of BASH shell scripts. This package consists of a master script (where users specify processing variables), and sub-scripts (the master script determines which of these are called, and in which order).
These scripts are used to process data related to my field... (1 Reply)
Discussion started by: msb65
1 Replies
4. Red Hat
Hi there,
I've started playing around with Linux a few days back, as part of my intenship. I was wondering if there is anyway I can install custom packages (non RPM packages...say like Oracle) as a part of Kickstart. My machines are running RHEL 4.
Thanks a lot :) (1 Reply)
Discussion started by: iman453
1 Replies
5. Red Hat
I have a file, ENV.doc somewhere in my home directory. I want to know where the file is located in my sub directories using FIND. But, I want to display only the relative path along with the file name.
Thanks, (6 Replies)
Discussion started by: ashok.g
6 Replies
6. Shell Programming and Scripting
The below hides the messy commands of wget
#!/bin/bash
cd 'C:\Users\cmccabe\Desktop\wget'
wget -O getCSV.txt http://172.24.188.113/data/getCSV.csv
progressfilt ()
{
local flag=false c count cr=$'\r' nl=$'\n'
while IFS='' read -d '' -rn 1 c
do
if $flag
... (5 Replies)
Discussion started by: cmccabe
5 Replies
7. Red Hat
Centos Behind The Proxy Server In My System , How Can I Set In Terminal Proxy ( Username & Password )
When Using The Command yum & rpm online I Will Respond Error
Thank You For Your Guidance (28 Replies)
Discussion started by: mnnn
28 Replies
8. Shell Programming and Scripting
Hello All,
I have a text file containing output from a command that contains lots of escape/control characters that when viewed using vi or view, looks like jibberish. But when viewed using the cat command the output is formatted properly.
Is there any way to take the output from the cat... (7 Replies)
Discussion started by: mrm5102
7 Replies
9. Solaris
Hello guys,
I'm new to this forum and got a question which may be quite uncommon. I created a custom IPS package (using this How to) with some software I have to install frequently to different Solaris 11 zones (MongoDB to be precise).
This software will be installed under "/opt/mongodb" and... (1 Reply)
Discussion started by: dheitepriem
1 Replies
10. Shell Programming and Scripting
i have data that can look like this:
echo "Master_Item_Service_is_down=0_njava_lang_NoClassDefFoundError=0_njava_lang_OutOfMemoryError=1_nemxCommonAppInitialization__Error_while_initializing=0_nINFO__Stopping_Coyote_HTTP_1_1_on_http_8080=7_nThe_file_or_directory_is_corrupted_and_unreadable=0_n" ... (7 Replies)
Discussion started by: SkySmart
7 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)