当您创建一个新的shell脚本时，您希望确保它尽可能没有问题，但是有时知道哪个shebang最适合您使用会有点混乱。在这一点上，今天的超级用户问答帖子回答了一个困惑读者的问题。

今天的问答环节是由SuperUser提供的，SuperUser是Stack Exchange的一个分支，是一个由社区驱动的问答网站分组。

问题

超级用户读者Hendre想知道什么时候最好使用#！/bin/bash而不是#！/shell脚本中的bin/sh：

When is it more appropriate to use #!/bin/bash rather than #!/bin/sh in a shell script?

什么时候最好用#！/bin/bash而不是#！/shell脚本中的bin/sh？

答案

超级用户贡献者grawity为我们提供了答案：

In short:

• There are several shells which implement a superset of the POSIX sh specification. On different systems, /bin/sh might be a link to ash, bash, dash, ksh, zsh, etc. It will always be sh-compatible though, never csh or fish.
• As long as you stick to sh features only, you can (and probably even should) use #!/bin/sh and the script should work fine, no matter which shell it is.
• If you start using bash-specific features (i.e. arrays), you should specifically request bash because, even if /bin/sh already invokes bash on your system, it might not on everyone else’s system, and your script will not run there. The same applies to zsh and ksh, of course.
• Even if the script is for personal use only, you might notice that some operating systems change /bin/sh during upgrades. For example, on Debian it used to be bash, but was later replaced with the very minimal dash. Scripts which used bashi**s but had #!/bin/sh suddenly broke.

However:

• Even #!/bin/bash is not that correct. On different systems, bash might live in /usr/bin, /usr/pkg/bin, or /usr/local/bin.
• A more reliable option is #!/usr/bin/env bash, which uses $PATH. Although the env tool itself is not strictly guaranteed either, /usr/bin/env still works on more systems than /bin/bash does.

有什么要补充的解释吗？在评论中发出声音。想从其他精通技术的Stack Exchange用户那里了解更多答案吗？在这里查看完整的讨论主题。

图片来源：维基百科