Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com X-Apparently-From: Message-ID: <3A82AB0A.7BAAFAE1@yahoo.com> Date: Thu, 08 Feb 2001 09:19:54 -0500 From: Earnie Boyd Reply-To: Earnie Boyd X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: cygwin-developers AT cygwin DOT com Subject: Re: A process can't have more than 63 child processes. References: <20010208090337 DOT A29571 AT redhat DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Christopher Faylor wrote: > > Yep. This has been noted before. The WaitForMultipleObjects > restriction makes it impractical to have more than 63 children. > > I guess we should set PSIZE to 64. > Your scope seems limiting. What about a Cygwin developed WaitForMultipleObjects? Perhaps even using the one from ReactOS. ;) I know, I know, where's the patch? Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com