Username/Email:  Password: 
TwitterFacebookFlickrRSS
Home ›

Bash Input Redirection

May 17, 2008  By Mitch Frazier
 in

If you use the shell you surely know about redirection: 

  # echo 'hello world' >output
  # cat <output
The first line writes "hello world" to the file "output", the second reads it back and writes it to standard output (normally the terminal).

Then there are "here" documents: 

  # cat <<EOF
  > hello
  > world
  > EOF
A "here" document is essentially a temporary, nameless file that is used as input to a command, here the "cat" command.

A less commonly seen form of here document is the "here" string: 

  # cat <<<'hello world'
In this form the string following the "<<<" becomes the content of the "here" document.

Another less commonly seen form of redirection is redirecting to a specific file descriptor: 

  # echo 'Error: oops' >&2
This redirects the output of the "echo" command to file descriptor 2, aka standard error. This is useful if you want to keep the error output of your scripts from contaminating the normal output when the output of your script is redirected.

These features work in bash and may not be available in other shells.

______________________

Mitch Frazier is an Associate Editor for Linux Journal.

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Here is an example of a way

Anonymous's picture
Submitted by Anonymous (not verified) on Fri, 09/04/2009 - 16:53.

Here is an example of a way to redirect command output without using a pipe.

while read line; do
echo This file: $line;
done <<EOF
$(ls)
EOF

Very useful. You could, for example, substitute ls for some program to query a database or sed commands for processing some files

I am not sure if this will run on old versions of bash though

It's worth mentioning some

Adam Backstrom's picture
Submitted by Adam Backstrom (not verified) on Tue, 05/20/2008 - 10:48.

It's worth mentioning some more examples of input redirection. For a file matched_files containing a list of files, you could grep the list:

grep mp3 < matched_files

Or do something to each file in the list:

while read line ; do
  flac "$line" && rm -f "$line"
done < matched_files

Lots more great examples are on the Useless Use of Cat Award page.

swap STDOUT and STDERR

Serge van Ginderachter's picture
Submitted by Serge van Ginderachter (not verified) on Sat, 05/17/2008 - 13:32.

swap STDOUT and STDERR: "3>&1 1>&2 2>&3"

as in:

(/usr/bin/$COMMAND $PARAM 3>&1 1>&2 2>&3 | grep -v $uninteresting_error ) 3>&1 1>&2 2>&3

Grep stderr

Mitch Frazier's picture
Submitted by Mitch Frazier on Sat, 05/17/2008 - 20:44.

In a bit more detail:

  • 3>&1 - moves file descriptor 1 (aka stdout) to file descriptor 3.
  • 1>&2 - moves file descriptor 2 (aka stderr) to file descriptor 1.
  • 2>&3 - moves file descriptor 3 to file descriptor 2 (aka stderr).
Similar to: 
   tmp    = stdout
   stdout = stderr
   stderr = tmp
and thereby swapping the standard out and the standard error. Which then allows the stderr (rather than stdout) to be piped into grep.

Mitch Frazier is an Associate Editor for Linux Journal.

To elaborate further

rak's picture
Submitted by rak (not verified) on Tue, 01/19/2010 - 17:15.

3>&1 redirects output sent to 3 to stdout,
1>&2 redirects output sent to stdout to stderr,
and 2>&3 redirects output sent to stderr to 3.

If you just want to include stderr output in your stdout along with the existing stdout output, you can just use 2>&1