zsh-users
 help / color / mirror / code / Atom feed
From: "Jérémie Roquet" <arkanosis@gmail.com>
To: Rory Mulvaney <rorymulv@gmail.com>
Cc: zsh-users@zsh.org, Wayne Davison <wayned@users.sourceforge.net>,
	 Anthony R Fletcher <arif@mail.nih.gov>
Subject: Re: wait for the next process to finish
Date: Tue, 13 Dec 2011 17:45:37 +0100	[thread overview]
Message-ID: <CAFOazAN9KMUHaUZCMj7usd_m6NwGERdRZ-9Mc+-oP8jbtbsHOg@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1112130937120.13348@MyComp.localdomain>

Hi,

2011/12/13 Rory Mulvaney <rorymulv@gmail.com>:
> To clarify (I think this is fairly simple), you can supply the process id
> as a parameter to 'wait', and though the $! method seems rather clumsy to
> retrieve the pid (since you have to retrieve it somehow in the next
> command after spawning the background process), it seems to work mostly in
> general.
>
> So you could do:
>
> sleep 20000 &
> sleep 20 &
> pid=$!
> wait $pid
>
> That will just wait for the sleep 20 process to complete while the sleep
> 20000 process still runs in the background.

Actually, it'll always wait for the last spawned job, not for the
first job to finish.

If you spawn them in the reverse order, ie:

sleep 20 &
sleep 20000 &
pid=$!
wait $pid

This will wait for the sleep 20000 process, even if the sleep 20 has
finished for long.

Best regards,

-- 
Jérémie


  reply	other threads:[~2011-12-13 16:46 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
2011-12-13  7:15   ` Martin Richter
2011-12-13 16:07   ` Rory Mulvaney
2011-12-13 16:45     ` Jérémie Roquet [this message]
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=CAFOazAN9KMUHaUZCMj7usd_m6NwGERdRZ-9Mc+-oP8jbtbsHOg@mail.gmail.com \
    --to=arkanosis@gmail.com \
    --cc=arif@mail.nih.gov \
    --cc=rorymulv@gmail.com \
    --cc=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).