X-Spam-Check-By: sourceware.org Date: Sun, 7 Jan 2007 12:23:41 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: `setfacl -m u:jdoe:rwx foo` returns 0, but file not writable by jdoe?? Message-ID: <20070107112341.GC10586@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <200701051934 DOT l05JYbCj030969 AT tigris DOT pounder DOT sol DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200701051934.l05JYbCj030969@tigris.pounder.sol.net> User-Agent: Mutt/1.4.2.2i Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Jan 5 13:34, Tom Rodman wrote: > Admittedly, this may be going "outside the cygwin perms model" a bit: > > In the below test case file 'foo' has it's RO file attribute set, then has > it's owner changed to someone other than the current user, has the posix > group set to None, the DACL protected, and all aces removed from the DACL. > > Next step is to run this (assumes we are user 'jdoe' [an administrator]): > > setfacl -m u:jdoe:rwx foo > > Above command returns 0 but jdoe can not write. The cause appears to > be that the windows RO file attribute is not unset by setfacl. I see the point. That old DOS R/O attribute is SO crappy on a file system which supports real permissions. Oh well... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/