通过结合PIPESTATUS[0]和在子shell中执行exit命令的结果，您可以直接访问初始命令的返回值:

命令| tee;退出${PIPESTATUS[0]}

这里有一个例子:

# the "false" shell built-in command returns 1
false | tee ; ( exit ${PIPESTATUS[0]} )
echo "return value: $?"

会给你:

返回值:1

在Ubuntu和Debian中，你可以apt-get install moreutils。这包含一个名为mispipe的实用程序，它返回管道中第一个命令的退出状态。

PIPESTATUS[@]必须在管道命令返回后立即复制到一个数组中。 任何对PIPESTATUS[@]的读取都将删除该内容。 如果计划检查所有管道命令的状态，则将其复制到另一个数组。 $?与${PIPESTATUS[@]}的最后一个元素值相同， 读它似乎破坏了“${PIPESTATUS[@]}”，但我还没有完全验证这一点。

declare -a PSA  
cmd1 | cmd2 | cmd3  
PSA=( "${PIPESTATUS[@]}" )

如果管道位于子外壳中，这将不起作用。为了解决这个问题， 查看bash pipestatus在backtick命令?

所以我想提供一个类似lesmana的答案，但我认为我的答案可能更简单，更有优势的纯伯恩壳解决方案:

# You want to pipe command1 through command2:
exec 4>&1
exitstatus=`{ { command1; printf $? 1>&3; } | command2 1>&4; } 3>&1`
# $exitstatus now has command1's exit status.

我认为最好从内到外解释这一点——command1将在标准输出(文件描述符1)上执行并打印其常规输出，然后一旦完成，printf将执行并在其标准输出上打印icommand1的退出代码，但该标准输出被重定向到文件描述符3。

While command1 is running, its stdout is being piped to command2 (printf's output never makes it to command2 because we send it to file descriptor 3 instead of 1, which is what the pipe reads). Then we redirect command2's output to file descriptor 4, so that it also stays out of file descriptor 1 - because we want file descriptor 1 free for a little bit later, because we will bring the printf output on file descriptor 3 back down into file descriptor 1 - because that's what the command substitution (the backticks), will capture and that's what will get placed into the variable.

The final bit of magic is that first exec 4>&1 we did as a separate command - it opens file descriptor 4 as a copy of the external shell's stdout. Command substitution will capture whatever is written on standard out from the perspective of the commands inside it - but since command2's output is going to file descriptor 4 as far as the command substitution is concerned, the command substitution doesn't capture it - however once it gets "out" of the command substitution it is effectively still going to the script's overall file descriptor 1.

(exec 4>&1必须是一个单独的命令，因为许多常见的shell不喜欢它，当您尝试在命令替换中写入文件描述符时，该命令替换在使用该替换的“external”命令中打开。所以这是最简单的便携方法。)

You can look at it in a less technical and more playful way, as if the outputs of the commands are leapfrogging each other: command1 pipes to command2, then the printf's output jumps over command 2 so that command2 doesn't catch it, and then command 2's output jumps over and out of the command substitution just as printf lands just in time to get captured by the substitution so that it ends up in the variable, and command2's output goes on its merry way being written to the standard output, just as in a normal pipe.

另外，据我所知，$?将仍然包含管道中第二个命令的返回代码，因为变量赋值、命令替换和复合命令对于其中命令的返回代码都是有效的透明的，因此command2的返回状态应该被传播出去——这一点，而不必定义额外的函数，这就是为什么我认为这可能是一个比lesmana提出的更好的解决方案。

根据lesmana提到的警告，command1可能在某些时候最终会使用文件描述符3或4，所以为了更健壮，你会这样做:

exec 4>&1
exitstatus=`{ { command1 3>&-; printf $? 1>&3; } 4>&- | command2 1>&4; } 3>&1`
exec 4>&-

注意，我在示例中使用复合命令，但是子shell(使用()而不是{}也可以工作，尽管可能效率较低)。

Commands inherit file descriptors from the process that launches them, so the entire second line will inherit file descriptor four, and the compound command followed by 3>&1 will inherit the file descriptor three. So the 4>&- makes sure that the inner compound command will not inherit file descriptor four, and the 3>&- will not inherit file descriptor three, so command1 gets a 'cleaner', more standard environment. You could also move the inner 4>&- next to the 3>&-, but I figure why not just limit its scope as much as possible.

我不确定直接使用文件描述符3和4的频率有多高——我认为大多数时候程序使用返回当前未使用的文件描述符的系统调用，但有时代码直接写入文件描述符3，我猜(我可以想象一个程序检查一个文件描述符，看看它是否打开，如果打开就使用它，如果没有打开则相应的行为不同)。因此，后者可能是最好记住并用于通用情况。

通过结合PIPESTATUS[0]和在子shell中执行exit命令的结果，您可以直接访问初始命令的返回值:

命令| tee;退出${PIPESTATUS[0]}

这里有一个例子:

# the "false" shell built-in command returns 1
false | tee ; ( exit ${PIPESTATUS[0]} )
echo "return value: $?"

会给你:

返回值:1

为什么不使用stderr?像这样:

(
     # Our long-running process that exits abnormally
    ( for i in {1..100} ; do echo ploop ; sleep 0.5 ; done ; exit 5 )
    echo $? 1>&2 # We pass the exit status of our long-running process to stderr (fd 2).
) | tee ploop.out

所以ploop。Out接收标准输出。Stderr接收长时间运行的进程的退出状态。这样做的好处是完全与posix兼容。

(好吧，除了示例长时间运行的进程中的range表达式，但这并不真正相关。)

这是它的样子:

...
ploop
ploop
ploop
ploop
ploop
ploop
ploop
ploop
ploop
ploop
5

请注意，返回代码5不会输出到文件plop .out。