X-Spam-Check-By: sourceware.org Message-ID: <4481D6A0.60302@cygwin.com> Date: Sat, 03 Jun 2006 14:36:16 -0400 From: "Larry Hall (Cygwin)" Reply-To: cygwin AT cygwin DOT com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051223 Fedora/1.5-0.2.fc4.remi Thunderbird/1.5 Mnenhy/0.7.3.0 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: rm not honoring directory access permissions References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 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: -- 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/