Re: `wait -n` returns 127 when it shouldn't

[Chet Ramey]

On 5/18/23 12:16 AM, Martin D Kealey wrote:

> If there is silent reaping going on (other than “wait -n” or “trap ... 
> SIGCHLD”) shouldn't the exit status and pid of each silently reaped process 
> be retained in a queue that “wait -n“ can extract from, in order to 
> maintain the reasonable expected semantics? Arguably this queue should be 
> shared with “fg” when job control is enabled.

There is always `silent reaping' going on. This is a red herring.

The problem was a race condition in the `wait -n' code.

--
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/