Re: bug in handling of ignored traps

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


> Per POSIX requirements on trap, dash is properly refusing to let
> non-interactive scripts reset signal handlers via trap if the shell was
> started with an inherited ignored signal handler.  However, dash lies to
> the user, making it impossible to tell if the user is invoking a shell
> in an environment where a signal was inherited as ignored.  ksh and bash
> are nicer about things, and at least let the user query whether a shell
> is treating a particular signal as non-resettable.

I don't think this is a bug.  It's more of a quality-of-implementation
issue.  dash appears to be following the "no error need be reported
when attempting to do so" part of the Posix spec, which is fine.  Bash
did more or less the same thing until bash-4.2.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU    chet@xxxxxxxx    http://cnswww.cns.cwru.edu/~chet/
--
To unsubscribe from this list: send the line "unsubscribe dash" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[LARTC]     [Bugtraq]     [Yosemite Forum]     [Photo]

Powered by Linux