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

[Chet Ramey]

On 5/19/23 6:24 AM, Robert Elz wrote:
>      Date:        Thu, 18 May 2023 14:07:32 -0400
>      From:        Chet Ramey <chet.ramey@case.edu>
>      Message-ID:  <fbd768c6-1a89-c3cf-dd4c-2b388265c73e@case.edu>
>
>    | This isn't a problem, and is a red herring. The code that manages that list
>    | makes sure to keep as many jobs in the list as POSIX requires, subject to
>    | the maxchild resource limit.
>
> That is good.
>
> Everyone else be aware that my previous response was based upon (rather
> incomplete) data from a message Chet sent me off list (because I sent him
> one off list, by accident really - the off list part).

I initially suspected the problem was with that code, and spent some time
chasing it before looking at the `wait -n' code itself and finding the
problem there.


--
``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/