Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Message-ID: <3B65835C.9000001@ece.gatech.edu>
Date: Mon, 30 Jul 2001 11:55:08 -0400
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010713
X-Accept-Language: en-us
MIME-Version: 1.0
To: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
CC: cygwin-developers AT sources DOT redhat DOT com
Subject: Re: Problems with autoconf-2.52 testsuite using current CVS Cygwin
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>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

 > Charles, did you check the permissions of the parent directory /tmp?
 > Is it possible that it still has permissions set so that it
 > propagatess them to files and subfolders?
 >
 > Could you repeat your test after calling
 >
 >	chmod 700 /tmp
 >	chmod 1777 /tmp
 >
 > ? The problem is mostly the already existing ACL. As I
 > wrote in my mail `NTSEC users: Please test' on this list:
 >
 > - `chmod 755' on a directory which already has 755 permissions.
 >
 >    Will not work since `chmod' is so _clever_ to do nothing
 >    if the requested permissions are the same as the current
 >    permissions.

Yes, that seems to be the problem w.r.t. the "cd /tmp, mkdir a, 
getfacl... tests" I was using.  However, I've discovered that my entire 
build tree (/usr/src/{autoconf, etc}/...) also has the 
problematic-looking acl.  So, I need to recursively chmod all around -- 
but the subdirs are owned by various users, so a simple script won't do. 
  Sigh.

(I mention this because of the <autoconf-build-dir>/tests/1/2/ problem I 
reported earlier.)

Anyway, after I finish cleaning up ACL's, I'll try the autoconf tests 
again -- maybe I too will then enjoy the VFORK bug...  :-P

--Chuck

P.S. Anybody know a good way of programmatically removing ACE's for 
"Administrator" and "Administrators" from every file/dir in a tree, 
*without* using that stupid inheritance property?