More Bash Redirections

 in

Everybody's seen redirection in bash commands, that's pretty common, but bash also allows you to define redirections when you define functions. This causes the redirections to be evaluated/executed whenever the function is called. This feature doesn't really give you any new features, just another way to express existing features.

The syntax for this is simple, you simply append the redirections onto the end of the function defintion:

function testy()
{
        ...
} < testy.in > testy.out 2> testy.err

Now whenever the function testy is called its input will come from testy.in, its output will go to testy.out and any errors will go to testy.err.

Since the redirections are evaluated when the function is called the redirection(s) can use variables and the variables are also evaluated when the function is called. So you could do something like this:

#!/bin/bash

function testy()
{
    echo testy westy
} >$out

out=jj1
testy
out=jj2
testy

This causes the output of the function to go to a different file with each call. The first call's output goes to jj1 and the second's to jj2:

$ bash j.sh; more jj?
::::::::::::::
jj1
::::::::::::::
testy westy
::::::::::::::
jj2
::::::::::::::
testy westy

As I mentioned earlier, there's not any real new capability here, you could also accomplish the same thing this way:

#!/bin/bash

function testy()
{
    echo testy westy
}

testy >jj1
testy >jj2

One possible use of this feature might be to put all your code inside a main function and then redirect it's error output so that you make sure it always gets captured:

#!/bin/bash

log=kk
function error()
{
    echo "$*" >&2
}
function testy()
{
    error testy westy
}

function testy2()
{
    error testy2 westy2
}

function main()
{
    testy
    testy2
} 2>$log

main

Running this produces:

$ bash k.sh ;cat kk
testy westy
testy2 westy2

Since bash also allows redirection to be included on {...} blocks/lists you could accomplish the same thing with the following:

#!/bin/bash

log=mm
function error()
{
    echo "$*" >&2
}
function testy()
{
    error testy westy
}

function testy2()
{
    error testy2 westy2
}

{
testy
testy2
} 2>$log

You can also use redirections on (...) blocks/lists but that causes the commands to be executed in a sub-shell, which isn't necessary here and which may cause problems since the sub-shell is a different process.

If you're wondering if you can override the redirections in the actual call, the answer is no. If you try to override them all that happens is that redirections in the call are executed/evaluated first then the ones in the function definition replace them. For example, in the following:

#!/bin/bash

function testy()
{
    echo testy westy
} >nn1

testy >nn2

The output file specified in the call (nn2) gets created but nothing gets written to it.

Also note that pipe "redirections" do not work, but here documents do:

#!/bin/bash

function testy()
{
    while read line
    do
        echo $line
    done
} <<EOF
hello
there
EOF

testy

Running this produces:

$ bash o.sh
hello
there
______________________

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.

an adjustment

ILGUIZ LATYPOV's picture

Just in case the script is interrupted with a Ctrl-C or a pipe overflow, two more signals could be treated by the trap block,


trap "
...
" EXIT SIGINT SIGPIPE

Please Help!

Jenny's picture

Um hi.

I've actually been wanting to use Linux Ubuntu, but I've been having trouble and don't really have anyone to help me.

This guy at school told me to use Linux Ubuntu and he said it's a really good program and gave me a CD that says "Ubuntu Warty". He said its the same as using a Mac. I put it in and double click on it and can't get it to work right.

I also try to go to Start/Add new programs/ and still can't figure it out.

I get really tired of XP and everything and really want to try something new.

Sorry I don't know much about computers.

more redirects

ILGUIZ LATYPOV's picture

#! /bin/bash
# This will redirect both stdout and stderr of all subsequent commands in the script.
exec 1> "${log_file}" 2>&1
set -x
OTHER_COMMANDS...


#! /bin/bash
# This will duplicate the the stdout/stderr capture to the screen almost synchronously.
log_file="log.txt"
tail -F "${log_file}" &
TAIL_PID=$!
trap "
        err=\$?
        set +x
        echo Exit code \$err
        sleep 2
        exec 2>&12 1>&11
        kill -HUP $TAIL_PID
        echo Exit code \$err >&2
        exit \$err
    " EXIT
exec 11>&1 12>&2 1> "${log_file}" 2>&1
set -x
OTHER_COMMANDS...
Webinar
One Click, Universal Protection: Implementing Centralized Security Policies on Linux Systems

As Linux continues to play an ever increasing role in corporate data centers and institutions, ensuring the integrity and protection of these systems must be a priority. With 60% of the world's websites and an increasing share of organization's mission-critical workloads running on Linux, failing to stop malware and other advanced threats on Linux can increasingly impact an organization's reputation and bottom line.

Learn More

Sponsored by Bit9

Webinar
Linux Backup and Recovery Webinar

Most companies incorporate backup procedures for critical data, which can be restored quickly if a loss occurs. However, fewer companies are prepared for catastrophic system failures, in which they lose all data, the entire operating system, applications, settings, patches and more, reducing their system(s) to “bare metal.” After all, before data can be restored to a system, there must be a system to restore it to.

In this one hour webinar, learn how to enhance your existing backup strategies for better disaster recovery preparedness using Storix System Backup Administrator (SBAdmin), a highly flexible bare-metal recovery solution for UNIX and Linux systems.

Learn More

Sponsored by Storix