Re: TEE bug?

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Please keep replies on the list, so that others may chime in.

According to Dean K. Gibson on 5/14/2008 6:38 PM:
| Actually, "trap - PIPE" didn't fix it, nor did "trap '' PIPE";  perhaps
| a bug in bash?  Anyway, I just use "2> /dev/null" (ugh), as this is in a
| trivial, manually run script anyway (I need to capture stdout, so I need
| to get rid of the messages), and I don't have the time to track down the
| problem in bash.

Which version of bash?  "trap '' PIPE" will cause the problem (it tells
bash to ignore SIGPIPE, and thus all of bash's child processes start with
it ignored).

Oh, Posix does state this:
http://www.opengroup.org/onlinepubs/009695399/utilities/trap.html

"Signals that were ignored on entry to a non-interactive shell cannot be
trapped or reset, although no error need be reported when attempting to do
so. An interactive shell may reset or catch signals ignored on entry."

So depending on whether you are seeing the error from a script or
interactively, this may factor in (ie. was SIGPIPE already ignored before
bash even started?).

|
| I do thank you for the information and time!

- --
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkgrirsACgkQ84KuGfSFAYDcjwCePBd4XOXgJ0vK116mswupNcDU
QxoAoMQZRUkxiIS8dyhDy22fbzbOtVZf
=1OQK
-----END PGP SIGNATURE-----