This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: rm not honoring directory access permissions
- From: "Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Sat, 03 Jun 2006 14:36:16 -0400
- Subject: Re: rm not honoring directory access permissions
- References: <C874DBE9D30B584587F8CD0EC34DA8BE01B1F4E9@EX00.idirect.net>
- Reply-to: cygwin at cygwin dot com
Nellis, Kenneth wrote:
I recently noticed that rm will delete a file without proper regard to the
access permissions of the containing directory. Researching the archives, I
see that this subject was touched on ("POSIX compliance of unlink(2)") in
February 2005, but the discussion seemed to veer off to a side issue (IMHO)
of updating various ctime's. So, I'm left wondering about the problem of
deleting the file. Is this a bug that ought to be fixed or what is the
rationale for maintaining the current behavior?
To remind anyone of the specific issue, consider the following in which rm
deletes (but shouldn't) file a/b:
$ mkdir a
$ touch a/b
$ chmod a-w a
$ rm a/b
I guess you missed the entire discussion on this and the subsequent
implementation. And it turns out that the implementation has the added
bonus of being documented in the User's Guide. :-) See the "(no)traverse"
option for the CYGWIN environment variable at:
<http://cygwin.com/cygwin-ug-net/using-cygwinenv.html>
--
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
838 Washington Street (508) 893-9889 - FAX
Holliston, MA 01746
--
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/