Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15268 > unrolled thread
| Started by | Earnestly <zibeon@googlemail.com> |
|---|---|
| First post | 2019-07-29 20:02 +0100 |
| Last post | 2019-07-29 20:02 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: How does this wait -n work to cap parallelism? Earnestly <zibeon@googlemail.com> - 2019-07-29 20:02 +0100
| From | Earnestly <zibeon@googlemail.com> |
|---|---|
| Date | 2019-07-29 20:02 +0100 |
| Subject | Re: How does this wait -n work to cap parallelism? |
| Message-ID | <mailman.187.1564426959.1985.bug-bash@gnu.org> |
On Mon, Jul 29, 2019 at 02:38:48PM -0400, Greg Wooledge wrote: > The same happens for my_job 7, and my_job 8. Each one is preceded by > a wait -n, so it waits for one of the existing jobs to terminate before > the new job is launched. This aspect of the behaviour isn't in question. Without reiterating too much, the question is about how that cap is maintained after the 'wait -n' loop only ever experiences a single agent while 'i' is incrementing, and only after 'i' has exceeded 'nproc' does the parallelism start.
Back to top | Article view | gnu.bash.bug
csiph-web