suspected bug in timeout command

[Rob Landley]

On 2/14/22 10:09 AM, Roberto A. Foglietta wrote:
>  However, if this bug shows-up, probably it means that the system has
> a lot of processes running and a lot of processes created and
> destroyed compared to the max PID available. Thus, the system might be
> incorrectly configured compared with its typical usage which probably
> is the main reason because nobody complained before.

Nah, a shell script can spin through an awful lot of PIDs pretty fast, and if
you're doing a -j 8 build that has a lot of script snippets (let alone parallel
autoconf etc) vs something with say a 10 second timeout?

Entirely plausible, and not a sign of a system being misconfigured. PIDs get
reused, fact of life, unix was already designed to cope back in the 1970s.

Rob