From: Wayne Davison <wayned@users.sourceforge.net>
To: zsh-users@zsh.org
Subject: Re: wait for the next process to finish
Date: Mon, 12 Dec 2011 11:41:30 -0800 [thread overview]
Message-ID: <CAHSx_Sv8g+tQQnytijXd=HOSHkyu-vwcmjCaDWoHhp2ba+whHw@mail.gmail.com> (raw)
In-Reply-To: <20111212154601.GA5198@cosy.cit.nih.gov>
[-- Attachment #1: Type: text/plain, Size: 765 bytes --]
On Mon, Dec 12, 2011 at 7:46 AM, Anthony R Fletcher <arif@mail.nih.gov>wrote:
> How can I wait for just the next job to finish?
>
One thing that may help you is TRAPCHLD. Sadly, the signal handler doesn't
tell you what pid it is reacting to, nor the exit code.
TRAPCHLD() {
echo here
oldpids=($pids)
pids=( )
for p in $oldpids; do
if kill -0 $p 2>/dev/null; then
pids+=$p
else
#wait $p # Sadly, this doesn't work
echo $p exited
fi
done
}
pids=( )
sleep 10 &
pids+=$!
sleep 20 &
pids+=$!
(sleep 15; false) &
pids+=$!
echo $pids
wait
echo done
It might be nice to set an environment parameter with the pid and status
info right before the dotrap(SIGCHLD) call in jobs.c.
..wayne..
next prev parent reply other threads:[~2011-12-12 19:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 15:46 Anthony R Fletcher
2011-12-12 16:37 ` TJ Luoma
2011-12-12 19:41 ` Wayne Davison [this message]
2011-12-13 7:15 ` Martin Richter
2011-12-13 16:07 ` Rory Mulvaney
2011-12-13 16:45 ` Jérémie Roquet
2011-12-13 16:59 ` Anthony R Fletcher
2011-12-13 18:08 ` Daniel Shahaf
2011-12-13 16:49 ` Christoph (Stucki) von Stuckrad
2011-12-13 17:31 ` Bart Schaefer
2011-12-13 17:04 ` Rory Mulvaney
2011-12-13 17:32 ` Anthony R Fletcher
2011-12-13 18:04 ` Jérémie Roquet
2011-12-13 18:20 ` Stephane Chazelas
2011-12-13 19:19 ` Anthony R Fletcher
2011-12-13 10:01 ` Peter Stephenson
2011-12-13 17:10 ` Bart Schaefer
2011-12-13 20:42 ` Rory Mulvaney
2011-12-13 17:45 ` Stephane Chazelas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHSx_Sv8g+tQQnytijXd=HOSHkyu-vwcmjCaDWoHhp2ba+whHw@mail.gmail.com' \
--to=wayned@users.sourceforge.net \
--cc=zsh-users@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).