Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Sun, 29 Sep 2002 23:10:21 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: Many pthread failures in the test suite, one setgroup failure Message-ID: <20020930031021.GA7906@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <20020929000215 DOT GB10872 AT redhat DOT com> <1033264646 DOT 4375 DOT 78 DOT camel AT lifelesswks> <20020929020609 DOT GB11549 AT redhat DOT com> <1033265603 DOT 4374 DOT 95 DOT camel AT lifelesswks> <20020929022338 DOT GA12659 AT redhat DOT com> <1033267203 DOT 4374 DOT 100 DOT camel AT lifelesswks> <20020929024420 DOT GA13416 AT redhat DOT com> <1033271512 DOT 4372 DOT 102 DOT camel AT lifelesswks> <3 DOT 0 DOT 5 DOT 32 DOT 20020929165333 DOT 0080fae0 AT mail DOT attbi DOT com> <3 DOT 0 DOT 5 DOT 32 DOT 20020929224948 DOT 00825140 AT h00207811519c DOT ne DOT client2 DOT attbi DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3.0.5.32.20020929224948.00825140@h00207811519c.ne.client2.attbi.com> User-Agent: Mutt/1.4i On Sun, Sep 29, 2002 at 10:49:48PM -0400, Pierre A. Humblet wrote: >At 07:33 PM 9/29/2002 -0400, Christopher Faylor wrote: >>>I also noticed that allow_ntsec == 1 on WinME, >>>which at the very least causes useless calls. >> >>How did allow_ntsec become 1 on WinME? That much at least should be >>easy to debug. > >Right. This afternoon I had noted it was already 1 when entering >environ_init. An fgrep just revealed in security.cc >BOOL allow_ntsec = true; >I would propose a patch setting it to false at the end of environ_init >on Win9X even if it is "on" in CYGWIN. Ditto for ntea and smbntsec. >Is there a better idea out there? I just activated the existing code in environ_init that turned this on in cygwin for OS's that support it. That's what I should have done before. If someone wants to set it on windows 95, I don't see why we should stop them. It might be useful for debugging. >>Also, another question is: Are you sure that you are using the latest >>CVS sources? This looks suspiciously like the problem which was just >>fixed. > >I have again updated from cvs and run make. Same result in gdb. Hopefully, you've run "make clean" and then "make". Just to be safe. cgf