Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Reply-To: Cygwin List Message-Id: <6.1.0.6.0.20040418190952.02f77ae8@127.0.0.1> X-Sender: Date: Sun, 18 Apr 2004 19:12:03 -0400 To: Thomas L Roche , cygwin AT cygwin DOT com From: Larry Hall Subject: Re: [OT?] make bash script wait for called program to finish? In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 06:20 PM 4/18/2004, you wrote: >How to make a bash script wait for a program that it calls to finish? >Why I ask: > >Don't ask me why this process is structured this way, but, in order to >install some code that I need in order to test my code, I hafta > >a wget an (executable) extractor and some (non-executable) binaries > >b run the extractor on the binaries. This runs some InstallShield UI > that no one I know seems to know how to script. This creates an > installer and a set of disk images. > >c run the installer on the images. Fortunately this part I know how to > script. > >What I'd really like to do is script the whole thing, because each >step takes about 30 min, but step b eludes me. So what I'd like my >script to do is > >0 wget > >1 launch the extractor UI, which I will briefly twiddle > >2 wait for the extractor to finish > >3 check that the installer and images were created > >4 run the installer on the images > >I know how to script everything but 2: how can I do that? > >Apologies if this is a FAQ: if so, please pass a pointer. If possible >please post to me as well as the list, and TIA. What did you try? Should we assume that 'wait' didn't work for you? -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/