On Sat, Mar 23, 2019 at 11:48:33AM -0400, Chet Ramey wrote:
> What's your goal here? If you want to associate an exit status with
> a process, you're going to have to save $! and wait for each process
> in turn.
My goal is to run a small process pool where upon one process
completes, another one
Hi all:
There's some inadvertently repeated text in doc/bashref.info which is
propagating into all manuals generated therefrom. Lines 1900 and 1901 in
the v5.0 version.
the rules described below (*note Pattern Matching::). If the
pattern matches If the pattern matches a trailing portion of the
I should have added in my previous reply, that using an
interactive shell to test this is useless, as even if
wait -n only returned one process, before the next command
prompt any other processes that have exited will be waited
upon and cleaned up anyway (and in that case, jobs type
output is appro
Date:Sat, 23 Mar 2019 11:48:33 -0400
From:Chet Ramey
Message-ID: <36545673-c287-6d8a-5e99-004ce9c6b...@case.edu>
| Yes. It waits for the next process to exit and then reaps all exited
| children.
That doesn't sound very useful. Our version (the NetBSD sh) finds
On 3/23/19 1:33 AM, Ben Elliston wrote:
> In bash 4.4.19, wait -n will collect the exit status of multiple
> processes if there are any -- not just one:
Yes. It waits for the next process to exit and then reaps all exited
children.
>
> bje@bapbop:~$ sleep 10 & sleep 10 & sleep 10 & sleep 10 &
>
On 3/22/19 11:02 PM, jake wrote:
> It is intermittent. Let's not give up just yet. I just reproduced it again
> after reading your response.
If you can reproduce it, a stack backtrace against a core dump would be
the most useful thing.
--
``The lyf so short, the craft so long to lerne.'' - Chauc
In bash 4.4.19, wait -n will collect the exit status of multiple
processes if there are any -- not just one:
bje@bapbop:~$ sleep 10 & sleep 10 & sleep 10 & sleep 10 &
[1] 13296
[2] 13297
[3] 13298
[4] 13299
bje@bapbop:~$ wait -n
[1] Donesleep 10
[2] Done
