This is the mail archive of the
mailing list for the Cygwin project.
Re: `setfacl -m u:jdoe:rwx foo` returns 0, but file not writable by jdoe??
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Sun, 7 Jan 2007 12:23:41 +0100
- Subject: Re: `setfacl -m u:jdoe:rwx foo` returns 0, but file not writable by jdoe??
- References: <200701051934.l05JYbCj030969@tigris.pounder.sol.net>
- Reply-to: 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 Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html