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 Subject: Re: Problems with autoconf-2.52 testsuite using current CVS Cygwin From: Robert Collins To: cygdev Cc: cygwin-developers AT sources DOT redhat DOT com In-Reply-To: <20010730101514.I490@cygbert.vinschen.de> References: <996329431 DOT 27668 DOT ezmlm AT sources DOT redhat DOT com> <3B63432E DOT 6050309 AT ece DOT gatech DOT edu> <3B649305 DOT 2090302 AT ece DOT gatech DOT edu> <3B64C0A9 DOT 1080700 AT ece DOT gatech DOT edu> <3B64F567 DOT 6060304 AT ece DOT gatech DOT edu> <20010730101514 DOT I490 AT cygbert DOT vinschen DOT de> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.11 (Beta Release) Date: 30 Jul 2001 19:13:36 +1000 Message-Id: <996484420.1960.1.camel@lifelesswks> Mime-Version: 1.0 X-OriginalArrivalTime: 30 Jul 2001 08:59:49.0715 (UTC) FILETIME=[FD238A30:01C118D5] On 30 Jul 2001 10:15:14 +0200, Corinna Vinschen wrote: > On Mon, Jul 30, 2001 at 01:49:27AM -0400, Charles Wilson wrote: > > Charles Wilson wrote: > > > > > > > > > > Changes by: corinna AT sources DOT redhat DOT com 2001-07-09 02:02:42 > > > Modified files: > > > winsup/cygwin : ChangeLog security.cc > > > Log message: > > > * security.cc (alloc_sd): Don't set inheritance attribute for > > > permissions given to directories. > > > > > > > Well, this is definitely the culprit; this change plus W2K/NTFS. I > > I still doubt that that is the problem for two reasons. > > First, I can't reproduce the below behaviour in a NTFS dir (which > isn't that evident, though). The directories have permissions > 700 as the testsuite creates them, the subordered files have > 644 permissions. Both shouldn't result in a problem to delete > the files. > > And second, as I already mentioned, the autoconf-2.52 testsuite > fails even in a /tmp on _FAT_ which is definitely not ntsec related. > > > don't get the problematic behavior on NT/NTFS. However, I know that > > Corinna put this in for a reason -- but I don't remember what it was. :-( Two thoughts: The main problem was the ash vfork issue meaning that the exit code wasn't running causing directory name collisions. Chuck has found a separate issue, related to the NTFS problem... Rob