在Shell腳本中，set -e的作用是讓腳本在任意命令執(zhí)行失?。ǚ祷胤橇銧顟B(tài)碼）時(shí)立即停止運(yùn)行。默認(rèn)情況下，Bash腳本會(huì)繼續(xù)執(zhí)行后續(xù)命令，即使某個(gè)命令已失敗，這可能導(dǎo)致錯(cuò)誤累積或產(chǎn)生意外結(jié)果。使用set -e后，腳本會(huì)在第一個(gè)失敗的命令處終止，例如：腳本執(zhí)行到false命令后將停止，后續(xù)命令不會(huì)運(yùn)行。然而，set -e并非完全可靠，存在一些例外情況：1. if條件中的命令不會(huì)觸發(fā)退出；2. 后接|| true的命令不會(huì)導(dǎo)致腳本退出；3. 管道命令中只有最后一個(gè)命令失敗才會(huì)觸發(fā)退出。為增強(qiáng)腳本健壯性，可結(jié)合set -o pipefail確保管道中任一命令失敗即退出。適合在自動(dòng)化部署或安裝腳本中使用，避免錯(cuò)誤擴(kuò)散；而在交互式腳本或需手動(dòng)處理錯(cuò)誤的場(chǎng)景中應(yīng)避免使用，建議顯式檢查返回碼進(jìn)行處理。

In a shell script, set -e tells the shell to stop executing the script immediately if any command exits with an error (i.e., returns a non-zero status). This is useful for making scripts safer by preventing them from continuing when something goes wrong.

Stops Script on First Error

By default, Bash scripts continue running even if one of the commands fails. That can lead to unexpected results or compound errors.

With set -e, as soon as a command fails, the script stops. For example:

#!/bin/bash
set -e

echo "Starting"
false
echo "This line won't run"

The output would be:

Starting

And then the script exits after false causes an error.

Note: Some commands might still continue depending on context — more on that in the next section.

Exceptions and Gotchas

Just because you use set -e doesn’t mean every failed command will stop the script. There are a few important exceptions:

• Commands in if conditions don’t trigger set -e. That’s intentional — you're usually checking whether something failed.
• Commands followed by || true won’t cause the script to exit either.
• Pipelines like command1 | command2 only trigger set -e if the last command in the pipeline fails.

So, while set -e helps catch many issues, it's not foolproof. You still need to be careful about how you structure your commands.

If you want stricter behavior, consider combining it with other options like set -o pipefail to make pipelines fail the script if any part fails.

When to Use It (and When Not To)

Use set -e when writing automation scripts where errors should stop execution — like deployment or setup scripts.

Avoid using it in interactive scripts or cases where you expect some failures and want to handle them manually. In those situations, it's better to check return codes explicitly:

some_command
if [ $? -ne 0 ]; then
  echo "Something went wrong, but I'll handle it here."
fi

Also, keep in mind that not all shells behave the same way with set -e, so if portability matters, test carefully.

It’s a handy flag but not magic — basically just makes scripts bail faster when things go south.

Ce qui précède est le contenu détaillé de. pour plus d'informations, suivez d'autres articles connexes sur le site Web de PHP en chinois!