It seems that 'trap 1 2 13 15' (without any command) reset the traps in a reasonably portable way,

I'm afraid not.  For example, on Ubuntu 9.04:

$ dash
!-penguin $ trap 1 2
!-penguin $ kill -2 $$
dash: 1: not found

It's hard to argue that this is a bug, since POSIX requires this behavior.

Better it would be to say: "On Solaris 9, /bin/sh may not execute a trap on exit if the trap is defined in a parenthesised sub-shell."

Yes, that sounds more accurate.


_______________________________________________
Autoconf mailing list
Autoconf@gnu.org
http://lists.gnu.org/mailman/listinfo/autoconf

Reply via email to