Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Sun, 10 Dec 2000 17:47:02 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Reproduced it finally
Message-ID: <20001210174702.A23010@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20001204203948 DOT 9541 DOT qmail AT web117 DOT yahoomail DOT com> <20001206121754 DOT E17209 AT pentek DOT com> <20001210170943 DOT A22677 AT redhat DOT com> <00121023370608 DOT 17980 AT cygbert>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <00121023370608.17980@cygbert>; from cygwin@cygwin.com on Sun, Dec 10, 2000 at 11:37:06PM +0100

On Sun, Dec 10, 2000 at 11:37:06PM +0100, Corinna Vinschen wrote:
>On Sunday 10 December 2000 23:09, Christopher Faylor wrote:
>> On Wed, Dec 06, 2000 at 12:17:55PM -0500, Charles Krug wrote:
>> >C:\Cygwin\bin\sh.exe: *** could not load advapi32.dll, Win32 error
>> > 998 0 [main] sh 177 sync_with_child: WaitForMultipleObjects timed
>> > out ./configure: Cannot fork: Resource temporarily unavailable
>>
>> Sounds like this problem:
>>
>> http://support.microsoft.com/support/kb/articles/Q196/0/69.ASP
>>
>> which, since it is based in advapi32.dll, sounds like a Windows NT
>> error. Possibly updating to a new service pack or not using
>> CYGWIN=ntsec may help.
>
>This is a nice one. I never saw that problem and I'm using
>ntsec since I developed it so I don't see the correlation
>between Win32 err 998 and ntsec. Any hint?

Sorry.  I should have been clearer.

The reason I mentioned ntsec is that many of the advapi32.dll functions
seem to be related to NT security, i.e. CYGWIN=ntsec.

I did not mean to imply that this was an actual problem with Cygwin's
ntsec code.  I doubt that that is the case.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com