> Do you see the patch kicking in, the "Found old pid..." message on stderr?
Yes, I get lots of these messages, when I used to get lots of errors.
Further analysis of my old strace output shows that the errors occurred when
pids had been reused.
> There is more to the story...
I'm fairly sure that
(Sorry if this doesn't appear in the right place - I'm still unable to
subscribe to the list and had to bodge a reply.)
I would just like to say that the patch specified in
http://cygwin.com/ml/cygwin/2004-09/msg00783.html fixes the problem that I
reported in http://cygwin.com/ml/cygwin/2004-09/ms
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
(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
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
5 matches
Mail list logo
