X-Spam-Check-By: sourceware.org Message-Id: <200701072018.l07KIwnk022580@tigris.pounder.sol.net> from: cygzx AT trodman DOT com (Tom Rodman) Reply-to: cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com Subject: Re: `setfacl -m u:jdoe:rwx foo` returns 0, but file not writable by jdoe?? In-reply-to: <20070107112341.GC10586@calimero.vinschen.de> References: <200701051934 DOT l05JYbCj030969 AT tigris DOT pounder DOT sol DOT net> <20070107112341 DOT GC10586 AT calimero DOT vinschen DOT de> Date: Sun, 07 Jan 2007 14:18:58 -0600 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 Sun 1/7/07 12:23 +0100 cygwin AT cygwin DOT com wrote: > 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... theory - these 2 steps will make *any* windows NTFS file, no matter what it's owner, group, perms, or file attributes are, writable by user "jdoe" (assuming it's not "in use"): setfacl -m u:jdoe:rwx foo # running as administrator "jdoe" cmd /c attrib -R foo # setacl step above allows the 'attrib' to work for user "jdoe" I appreciate the power in setfacl. :-> -- Tom -- 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/