[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: wait -n shouldn't collect multiple processes
|
From: |
Chet Ramey |
|
Subject: |
Re: wait -n shouldn't collect multiple processes |
|
Date: |
Tue, 26 Mar 2019 08:39:00 -0400 |
|
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.6.0 |
On 3/26/19 8:12 AM, Robert Elz wrote:
> Date: Tue, 26 Mar 2019 10:55:53 +0100
> From: Andreas Schwab <schwab@suse.de>
> Message-ID: <mvmimw6t0wm.fsf@suse.de>
>
> | Even better, IMHO: "wait waits for the next job to terminate"
>
> Something should allow for there being no waiting involved at all
> if some job has already terminated but has not been waited for.
Why? `wait -n' collects the exit statuses of terminated jobs one at
a time. It's not really important to detail how much time is spent
waiting.
--
``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/
- Re: wait -n shouldn't collect multiple processes, (continued)
Re: wait -n shouldn't collect multiple processes, Robert Elz, 2019/03/25