The change is far from trivial or harmless, if it was intended. I had to
rebuild a custom server I run in a hurry because it was flooding an IRC
channel with log lines a backend bash script sent to stderr. And I can
think of plenty of ways to trash files with this bug.
Anyway, thanks a lot Sté
Andreas Schwab wrote:
I get this:
$ bash -c 'trap "" PIPE; sleep 1; echo a; echo b > a' | :
bash: line 0: echo: write error: Broken pipe
and the file contains only one line.
Andreas.
I did more tests, and this is what I came up with:
- akula, my bleeding edge box, is a Debian-unstable box
Configuration Information [Automatically generated, do not change]:
Machine: i486
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='
