Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: wait gets confused when second argument exits before first (i think)
- X-seq: zsh-workers 27872
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh workers <zsh-workers@xxxxxxx>
- Subject: Re: wait gets confused when second argument exits before first (i think)
- Date: Fri, 09 Apr 2010 20:31:41 -0700
- In-reply-to: <h2g237967ef1004091837w851e3e48sf5765f11027448a8@xxxxxxxxxxxxxx>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <h2g237967ef1004091837w851e3e48sf5765f11027448a8@xxxxxxxxxxxxxx>
On Apr 10, 3:37am, Mikael Magnusson wrote:
}
} So it looks like it doesn't matter if %1 or %2 exits first, just which
} is the first argument to wait.
The wait isn't performed in parallel for all the argument PIDs at once
(it's not like doing a select() on a list of file descriptors). Rather
the shell waits for each PID in the order it appears on the command
line, before attempting to wait on the next one.
See zsh-workers/27442 and its thread for possibly-related discussion;
there doesn't appear to be a requirement that the shell keep track of
more than one already-exited asynchronous job.
--
Messages sorted by:
Reverse Date,
Date,
Thread,
Author