I also include set -o pipefail (exit if ANY command in a pipeline fails). Had to...

nwalfield · on March 24, 2015

set -o pipefail makes common idioms a pain. Consider using head, which simply exits after it has read a few lines. In this case, the input process gets a SIGPIPE and exits with a non-zero exit code:

Consider /tmp/test.sh:

  set -o pipefail
  yes foo | head

  $ bash /tmp/test.sh >/dev/null
  $ echo $?
  141

pixelbeat · on March 24, 2015

That's a bug IMHO which I reported at http://lists.gnu.org/archive/html/bug-bash/2015-02/msg00052....

I've collated other mishandling of closed pipes at: http://www.pixelbeat.org/programming/sigpipe_handling.html

quotemstr · on March 24, 2015

For a while now, I've thought we should change SIGPIPE's SIG_DFL action to _exit(0).