Redirect all subsequent commands' stderr using exec

Question

I have a bash file that I need to redirect all output to one file, debug log as well as to the terminal. I need to redirect both stdout and stderr to the debug and log it for all commands in the script.

I do not want to add 2>&1 | tee -a $DEBUG for every single command in the file. I could live with | tee -a $DEBUG.

I remember there was a way to do it with something like exec 2>&1.

Currently I'm using something like the following:

#!/bin/bash
DEBUGLOG=/tmp/debug
exec 2>&1
somecommand | tee -a $DEBUGLOG
somecommand2 | tee -a $DEBUGLOG
somecommand3 | tee -a $DEBUGLOG

but it does not work. Does anyone have a solution/can explain the cause?

Answer 1

You can use exec like this at the top of your script:

exec > >(tee "$HOME/somefile.log") 2>&1

For example:

#!/bin/bash -

exec > >(tee "$HOME/somefile.log") 2>&1

echo "$HOME"
echo hi
date
date +%F
echo bye 1>&2

Gives me output to the file $HOME/somefile.log and to the terminal like this:

/home/saml
hi
Sun Jan 20 13:54:17 EST 2013
2013-01-20
bye

Answer 2

As for a solution to redirect lots of command at once:

#!/bin/bash
{
    somecommand 
    somecommand2
    somecommand3
} 2>&1 | tee -a $DEBUGLOG

Why your original solution does not work: exec 2>&1 will redirect the standard error output to the standard output of your shell, which, if you run your script from the console, will be your console. the pipe redirection on commands will only redirect the standard output of the command.

On the point of view of somecommand, its standard output goes into a pipe connected to tee and the standard error goes into the same file/pseudofile as the standard error of the shell, which you redirect to the standard output of the shell, which will be the console if you run your program from the console.

The one true way to explain it is to see what really happens:

Your shell's original environment might look like this if you run it from the terminal:

stdin -> /dev/pts/42
stdout -> /dev/pts/42
stderr -> /dev/pts/42

After you redirect standard error into standard output (exec 2>&1), you ... basically change nothing. But if you redirect the script's standard output to a file, you would end up with an environment like this:

stdin -> /dev/pts/42
stdout -> /your/file
stderr -> /dev/pts/42

Then redirecting the shell standard error into standard output would end up like this :

stdin -> /dev/pts/42
stdout -> /your/file
stderr -> /your/file

Running a command will inherit this environment. If you run a command and pipe it to tee, the command's environment would be :

stdin -> /dev/pts/42
stdout -> pipe:[4242]
stderr -> /your/file

So your command's standard error still goes into what the shell uses as its standard error.

You can actually see the environment of a command by looking in /proc/[pid]/fd: use ls -l to also list the symbolic link's content. The 0 file here is standard input, 1 is standard output and 2 is standard error. If the command opens more files (and most programs do), you will also see them. A program can also choose to redirect or close its standard input/output and reuse 0, 1 and 2.

Answer 3

Write stderr and stdout to a file, display stderr on screen (on stdout)

exec 2> >(tee -a -i "$HOME/somefile.log")
exec >> "$HOME/somefile.log"

Useful for crons, so you can receive errors (and only errors) by mail

Answer 4

Based on Capture all the output of a script to a file (from the script itself)

#!/usr/bin/env bash

if [ -z "$SCRIPT" ]; then
  export SCRIPT="$0"
  /usr/bin/script -a logfile.txt /bin/bash -c "$0 $*"
  exit 0
fi
echo

Answer 5

The script man page has some warnings:

It is not recommended to run script in non-interactive shells. The inner shell of script is always interactive, and this could lead to unexpected results.

You should also avoid use of script in command pipes, as script can read more input than you would expect.

I take this such that script is not safe to use when stdin and/or stdout are going to be redirected.

I'd to something like this when running commands:

output=$("<command> <args>" 2> tee -a $LOGFILE >&2)

It is understood that the OP doesn't want to do exactly that for every command but you can easily define a function

run () { ... output=$("$(@) 2> tee -a $LOGFILE >&2"; ... }

Which enables you to capture the regular output and working on it while logging the warnings and errors and also displaying them on stderr at the same time.

You could then do

[ $? -eq 0 ] && echo "<command> <args> succeeded! Output:\n$output\n(EOF)" >>$LOGFILE

to also log the regular output if desired.

Answer 6

All output goes to yourscript.sh.log in directory were script was called and also displays output in terminal.

#!/bin/bash

logfile=$(pwd)/${0##*/}.log
truncate -s0 "$logfile"
exec > >(tee -a "$logfile") 2>&1

!!IMPORTANT!! If you do not have #!/bin/bash on the first line, you may get a syntax error.

Credits: This is a modded version from one of the geniuses who works for Rocky Linux. Can't remember who. Thank you Rocky Linux Devs!