I'm trying to understand why whenever I'm using function 2>&1 | tee -a $LOG
tee creates a subshell in function that can't be exited by simple exit 1
(and if I'm not using tee
it works fine). Below the example:
#!/bin/bash
LOG=/root/log.log
function first()
{
echo "Function 1 - I WANT to see this."
exit 1
}
function second()
{
echo "Function 2 - I DON'T WANT to see this."
exit 1
}
first 2>&1 | tee -a $LOG
second 2>&1 | tee -a $LOG
Output:
[root@linuxbox ~]# ./1.sh
Function 1 - I WANT to see this.
Function 2 - I DON'T WANT to see this.
So. if I remove | tee -a $LOG
part, it's gonna work as expected (script will be exited in the first function).
Can you, please, explain how to overcome this and exit properly in the function while being able to tee output?
Use
PIPESTATUS
to retrieve the exit status of the first command in the pipeline.You can tell bash to fail if anything in the pipeline fails with
set -e -o pipefail
:If you create a pipeline, the function is run in a subshell, and if you
exit
from a subshell, only the subshell will be affected, not the parent shell.If, instead of
aFunction | tee
you do:it'll be essential the same, except
aFunction
won't run in a subshell, and thus will be able to affect the current environment (set variables, call exit, etc.).