On 5/10/17 8:47 AM, shwares...@aol.com wrote:
> Yes, reception can be blocked for reasons outside a scripts control before
> an action is set with trap, but the standard does speak to when signals are
> to be raised and delivery attempted.
That's all the standard can guarantee. The standard does not guarantee that
each child exit will generate a separate SIGCHLD delivery. There is also
nothing in the standard that speaks to what a shell, for instance, does
when it receives a signal. For instance, there is nothing preventing a
shell from reaping multiple children when it receives a single SIGCHLD and
running a single instance of the SIGCHLD trap as a result.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
