On 29 May 2006 02:53, Tom Rodman wrote:
> <sorry for mime header mistake on last post, this is same post w/fixed
> header> I tried the test case below w/the 5/27 snapshot and got
> what appear to be the same fork errors. So, I'm sticking
> with the 4/3/2006 snapshot.
>
> Is there any other info I can supply to help?
Yep. Can you run process explorer and take a look at the shell that's
running the script - i.e. the fork parent - and see if it's leaking thousands
of file handles to pipes with names of a form like:
\Device\NamedPipe\Win32Pipes.0000055c.0000003e
(hex numbers will vary).
cheers,
DaveK
--
Can't think of a witty .sigline today....
--
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/
