Sponsored Content
Full Discussion: Standard Output
Top Forums Shell Programming and Scripting Standard Output Post 51513 by google on Friday 21st of May 2004 05:08:52 PM
Old 05-21-2004
Quote:
somecommand | tee output_file
Use the tee -a flag to append your output to a file. You can also redirect both standard out (STDOUT) and standard error (STDERR) streams to a file using their respective file descriptors.

Code:
Example:

 command > file 2>&1

 or to append to the file:

command >> file 2>&1

 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Standard output not redirected from /bin/sh

I have an application which has a lot of cout & cerr statements. This application also opens a log file (for eg a.log). When this application is run from the inittab file as follows /bin/sh -c " . /etc/timezone; exec /test" all the cout & cerr statements are printed in the log file... (1 Reply)
Discussion started by: soorajmu
1 Replies

2. Shell Programming and Scripting

Standard output and redirection

Hello, Is is possible to redirect stdout to a file as well as to the console/screen or display in ksh. any thoughts suggestions/input is appreciated. Thanks. (2 Replies)
Discussion started by: jerardfjay
2 Replies

3. Shell Programming and Scripting

Rewriting standard output lines

Hello I'm curious about how to get a bash script to rewrite a line of standard output. For example, many programs track their progress by writing percentages on the screen: Precent Done: 60% That line gets updated periodically to reflect the status.. My question, is how do we do this, as... (5 Replies)
Discussion started by: neked
5 Replies

4. Shell Programming and Scripting

Command Output to Standard Input

Hi All, How do I provide the output of a command to another command which is waiting for an input from the user ? Ex : I need to login to a device via telnet. In the script, initially I use the "read" command to get the IP Address, Username and Password of the device from the user. Now,... (1 Reply)
Discussion started by: sushant172
1 Replies

5. UNIX for Dummies Questions & Answers

Redirect Standard output and standard error into spreadsheet

Hey, I'm completely new at this and I was wondering if there is a way that I would be able to redirect the log files in a directories standard output and standard error into and excel spreadsheet in anyway? Please remember don't use too advanced of terminology as I just started using shell... (6 Replies)
Discussion started by: killaram
6 Replies

6. Shell Programming and Scripting

How redirect standard output to a file

Hi guys, i have a script named purgeErrors.ksh, when i execute this script i need to redirect the output to a log file in the same directory, how can i do that ?? -- Aditya (5 Replies)
Discussion started by: chaditya
5 Replies

7. Shell Programming and Scripting

How to execute standard output ?

Alright so i got this script genpipe: echo "$*" |sh genscript file vi file << 'HERE' :%s/^/echo /g :%s/ $//g :%s/ /&\| xargs \.\/plus /g :wq HERE cat file Which generates output like echo 1 | xargs ./plus 2 | xargs ./plus 3 and so on Now i got the next script multiplus, who should... (3 Replies)
Discussion started by: Bertieboy7
3 Replies

8. Red Hat

Command understanding the output file destination in case of standard output!!!!!

I ran the following command. cat abc.c > abc.c I got message the following message from command cat: cat: abc.c : input file is same as the output file How the command came to know of the destination file name as the command is sending output to standard file. (3 Replies)
Discussion started by: ravisingh
3 Replies

9. Shell Programming and Scripting

Output mean and standard deviation of a row

I have a file that looks that this: 820 890 530 1650 1600 1800 1850 1900 2270 1640 2300 1670 2080 2200 2350 1150 1630 2210 I would like to output the mean and standard deviation of each row so that my final output would look like this 820 890 530 746.667 155.849 1650 1600 1800... (5 Replies)
Discussion started by: kayak
5 Replies

10. Shell Programming and Scripting

SU and Standard Output

Bit of a strange one. Have a script called rapidclone_test.sh which calls Oracle rapidclone using su -c as an oracle osuser. However, if I control+c out to the calling shell anything entered is not displayed on the terminal. Any command executes successfully though. Why is the standard... (1 Reply)
Discussion started by: u20sr
1 Replies
TEE(P)							     POSIX Programmer's Manual							    TEE(P)

NAME
tee - duplicate standard input SYNOPSIS
tee [-ai][file...] DESCRIPTION
The tee utility shall copy standard input to standard output, making a copy in zero or more files. The tee utility shall not buffer output. If the -a option is not specified, output files shall be written (see File Read, Write, and Creation . OPTIONS
The tee utility shall conform to the Base Definitions volume of IEEE Std 1003.1-2001, Section 12.2, Utility Syntax Guidelines. The following options shall be supported: -a Append the output to the files. -i Ignore the SIGINT signal. OPERANDS
The following operands shall be supported: file A pathname of an output file. Processing of at least 13 file operands shall be supported. STDIN
The standard input can be of any type. INPUT FILES
None. ENVIRONMENT VARIABLES
The following environment variables shall affect the execution of tee: LANG Provide a default value for the internationalization variables that are unset or null. (See the Base Definitions volume of IEEE Std 1003.1-2001, Section 8.2, Internationalization Variables for the precedence of internationalization variables used to determine the values of locale categories.) LC_ALL If set to a non-empty string value, override the values of all the other internationalization variables. LC_CTYPE Determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multi-byte characters in arguments). LC_MESSAGES Determine the locale that should be used to affect the format and contents of diagnostic messages written to standard error. NLSPATH Determine the location of message catalogs for the processing of LC_MESSAGES . ASYNCHRONOUS EVENTS
Default, except that if the -i option was specified, SIGINT shall be ignored. STDOUT
The standard output shall be a copy of the standard input. STDERR
The standard error shall be used only for diagnostic messages. OUTPUT FILES
If any file operands are specified, the standard input shall be copied to each named file. EXTENDED DESCRIPTION
None. EXIT STATUS
The following exit values shall be returned: 0 The standard input was successfully copied to all output files. >0 An error occurred. CONSEQUENCES OF ERRORS
If a write to any successfully opened file operand fails, writes to other successfully opened file operands and standard output shall con- tinue, but the exit status shall be non-zero. Otherwise, the default actions specified in Utility Description Defaults apply. The following sections are informative. APPLICATION USAGE
The tee utility is usually used in a pipeline, to make a copy of the output of some utility. The file operand is technically optional, but tee is no more useful than cat when none is specified. EXAMPLES
Save an unsorted intermediate form of the data in a pipeline: ... | tee unsorted | sort > sorted RATIONALE
The buffering requirement means that tee is not allowed to use ISO C standard fully buffered or line-buffered writes. It does not mean that tee has to do 1-byte reads followed by 1-byte writes. It should be noted that early versions of BSD ignore any invalid options and accept a single '-' as an alternative to -i. They also print a message if unable to open a file: "tee: cannot access %s ", <pathname> Historical implementations ignore write errors. This is explicitly not permitted by this volume of IEEE Std 1003.1-2001. Some historical implementations use O_APPEND when providing append mode; others use the lseek() function to seek to the end-of-file after opening the file without O_APPEND. This volume of IEEE Std 1003.1-2001 requires functionality equivalent to using O_APPEND; see File Read, Write, and Creation . FUTURE DIRECTIONS
None. SEE ALSO
Introduction , cat , the System Interfaces volume of IEEE Std 1003.1-2001, lseek() COPYRIGHT
Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1, 2003 Edition, Standard for Information Technol- ogy -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2003 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html . IEEE
/The Open Group 2003 TEE(P)
All times are GMT -4. The time now is 05:48 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy