RE: bash script doesn't wait for commands to complete

2004-09-17 Thread Dolton Tony AB
I've now realised that this is actually the same problem as described in the thread "Re: Bash returns incorrect process status" - it's the fact that bash is reusing process ids that is causing the problem. I've tried the patch in http://cygwin.com/ml/cygwin/2004-09/msg00783.html and it prevents the

Re: bash script doesn't wait for commands to complete -- me too

2004-09-10 Thread Eric Hanchrow
> "Dolton" == Dolton Tony AB <[EMAIL PROTECTED]> writes: >> >> So, if you are starting more than around 62 subprocesses then >> things probably won't work right. >> >> cgf Dolton> Thanks for that. However, although the problem occurs Dolton> most frequently with

RE: bash script doesn't wait for commands to complete

2004-09-10 Thread Dolton Tony AB
(Sorry if this doesn't appear in the right place - I've been unable to subscribe to the list and had to bodge a reply.) >>I have a problem whereby a bash script doesn't wait for foreground commands >>to complete. The script in question kicks off a number of background >>processes, and processes th

Re: bash script doesn't wait for commands to complete

2004-09-09 Thread Christopher Faylor
On Thu, Sep 09, 2004 at 04:20:19PM +0100, Dolton Tony AB wrote: >I have a problem whereby a bash script doesn't wait for foreground commands >to complete. The script in question kicks off a number of background >processes, and processes their results as they complete. > >A simplified version which

bash script doesn't wait for commands to complete

2004-09-09 Thread Dolton Tony AB
I have a problem whereby a bash script doesn't wait for foreground commands to complete. The script in question kicks off a number of background processes, and processes their results as they complete. A simplified version which exhibits the problem is attached as scr.sh. The number of background