12-05-2011
File descriptor 2 is standard error, stderr. File descriptor 1 is standard output, stdout. This will make sure any output sent to stderr is redirected to stdout, which in turn was attached to the file /tmp/proc.
Bash manual on Redirections is a good read on the subject.
Last edited by neutronscott; 12-05-2011 at 04:29 AM..
Reason: grammar
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
I'm trying to locate all files that do not contain the string /usr but do contain the string csh within the file called /etc/passwd. Then I would like to direct this output to a file called pout.
Does anyone one have suggestions on this one?
Thanks (2 Replies)
Discussion started by: klannon
2 Replies
2. UNIX for Dummies Questions & Answers
How do I direct the output of an at command
at now < backupprogram
so that I see something happening. It says the job has been executed but I am not getting the tar file that my backup program on the computer anywhere at all
Please help me - I really am a struggling begginer. (1 Reply)
Discussion started by: Cynergetix
1 Replies
3. UNIX for Advanced & Expert Users
Hi,
I'm running a program by executing the following command...
convert NA 2> compiler.err
Here is the command for debugging this process in IBM debugger...
idebug convert NA 2> compiler.err
On executing the above command the error output from idebug process is
redirected to compiler.err,... (3 Replies)
Discussion started by: fermisoft
3 Replies
4. Programming
Hi,
I just wrote a program in C to split a comma seperated string in to group of strings using strtok() function. The code is:
int main()
{
char *temp;//not used here but basically we extract one string after another using strtok() and assign to a string pointer defined like this.
... (3 Replies)
Discussion started by: SankarV
3 Replies
5. Shell Programming and Scripting
When I do
time tar cvf /dev/st0 /mnt/junk >> /root/benchlog, I want it to put the output of the time command into the benchlog file, but it put /mnt/junk. How do I get it to put the output of the tar command? (1 Reply)
Discussion started by: jeriryan87
1 Replies
6. Shell Programming and Scripting
I have a script in which some outputs are directed to one file
echo "Load Started" >>${LOGFILE1}
If I have another file LOGFILE2 and i want to redirect the output of the above echo command to LOGFILE2 as well with the same command line... how can i do that?
Thanks (2 Replies)
Discussion started by: cobroraj
2 Replies
7. Shell Programming and Scripting
Dear All
I have a simple bash script that creates a folder ( I called it TEMP) in the current directory.
The question is: how do I direct the output of my awk script into folder TEMP?
Below is my attempt:
#!/bin/bash
mkdir TEMP
echo Enter input file:
read infile
awk... (4 Replies)
Discussion started by: Ghetz
4 Replies
8. Shell Programming and Scripting
Is there a way to keep the output of a script displayed on the terminal when it's run by itself, but suspend part of that output and only have a specific part delivered when it's piped to another script or program? I'm thinking something like the following pseudocode:
#!/bin/bash
... (1 Reply)
Discussion started by: trigg
1 Replies
9. Shell Programming and Scripting
Hi,
I still have the problem with directing information from cat or grep to a variable.
For instance:
XMSG "$(date +%Y_%m_%d)_error_report.txt" "$(cat "$(date +%Y_%m_%d)_error_report.txt")" &Works! The text received by cat is directed to my function.
If it is written like this, my... (2 Replies)
Discussion started by: haukee
2 Replies
10. Shell Programming and Scripting
Hi All,
Have scheduled a cron entry to run once a week.
0 0 * * 1 /export/home/nz/history_load/prod/LoadManager.sh >>/dev/null 2>&1
Not sure, why this job did not got triggered last week. Want to know the reason behind not getting triggered.
I was re-directing the output of... (1 Reply)
Discussion started by: Nagaraja Akkiva
1 Replies
STDIN(3) Linux Programmer's Manual STDIN(3)
NAME
stdin, stdout, stderr - standard I/O streams
SYNOPSIS
#include <stdio.h>
extern FILE *stdin;
extern FILE *stdout;
extern FILE *stderr;
DESCRIPTION
Under normal circumstances every Unix program has three streams opened for it when it starts up, one for input, one for output, and one for
printing diagnostic or error messages. These are typically attached to the user's terminal (see tty(4) but might instead refer to files or
other devices, depending on what the parent process chose to set up. (See also the "Redirection" section of sh(1).)
The input stream is referred to as "standard input"; the output stream is referred to as "standard output"; and the error stream is
referred to as "standard error". These terms are abbreviated to form the symbols used to refer to these files, namely stdin, stdout, and
stderr.
Each of these symbols is a stdio(3) macro of type pointer to FILE, and can be used with functions like fprintf(3) or fread(3).
Since FILEs are a buffering wrapper around Unix file descriptors, the same underlying files may also be accessed using the raw Unix file
interface, that is, the functions like read(2) and lseek(2).
On program startup, the integer file descriptors associated with the streams stdin, stdout, and stderr are 0, 1, and 2, respectively. The
preprocessor symbols STDIN_FILENO, STDOUT_FILENO, and STDERR_FILENO are defined with these values in <unistd.h>. (Applying freopen(3) to
one of these streams can change the file descriptor number associated with the stream.)
Note that mixing use of FILEs and raw file descriptors can produce unexpected results and should generally be avoided. (For the masochis-
tic among you: POSIX.1, section 8.2.3, describes in detail how this interaction is supposed to work.) A general rule is that file descrip-
tors are handled in the kernel, while stdio is just a library. This means for example, that after an exec(3), the child inherits all open
file descriptors, but all old streams have become inaccessible.
Since the symbols stdin, stdout, and stderr are specified to be macros, assigning to them is nonportable. The standard streams can be made
to refer to different files with help of the library function freopen(3), specially introduced to make it possible to reassign stdin, std-
out, and stderr. The standard streams are closed by a call to exit(3) and by normal program termination.
CONFORMING TO
The stdin, stdout, and stderr macros conform to C89 and this standard also stipulates that these three streams shall be open at program
startup.
NOTES
The stream stderr is unbuffered. The stream stdout is line-buffered when it points to a terminal. Partial lines will not appear until
fflush(3) or exit(3) is called, or a newline is printed. This can produce unexpected results, especially with debugging output. The
buffering mode of the standard streams (or any other stream) can be changed using the setbuf(3) or setvbuf(3) call. Note that in case
stdin is associated with a terminal, there may also be input buffering in the terminal driver, entirely unrelated to stdio buffering.
(Indeed, normally terminal input is line buffered in the kernel.) This kernel input handling can be modified using calls like tcse-
tattr(3); see also stty(1), and termios(3).
SEE ALSO
csh(1), sh(1), open(2), fopen(3), stdio(3)
COLOPHON
This page is part of release 3.27 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 2008-07-14 STDIN(3)