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 Message-Id: <4.3.1.2.20030121225229.01747990@pop.rcn.com> X-Sender: lhall AT pop DOT rcn DOT com Date: Tue, 21 Jan 2003 22:59:13 -0500 To: Shankar Unni , cygwin AT cygwin DOT com From: "Larry Hall (RFK Partners, Inc)" Subject: Re: Bug in rm -r with locked files In-Reply-To: <3E2DBDFC.9050103@cotagesoft.com> References: <232810-220031221163510989 AT M2W098 DOT mail2web DOT com> <5 DOT 2 DOT 0 DOT 9 DOT 2 DOT 20030121111136 DOT 0286aea0 AT pop3 DOT cris DOT com> <20030121201944 DOT GE17833 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 04:39 PM 1/21/2003, Shankar Unni wrote: >Christopher Faylor wrote: > >>It's not a completely intractable problem. I think that someone (Chris >>January?) provided a workaround at one point. "cygserver" could also >>provide a possible solution someday. > >Right. I went back and re-read those archives. Interesting problem. > >Now why was it important to do this "delayed remove" semantics? I.e. what (as alluded to by Robert Collins) would be broken if unlink simply returned EPERM or something like that if the file was busy? I didn't see any reference to that in the message threads. Forgive me. I didn't take the time to review the email archives for all the threads on this but if I recall correctly, the current behavior is meant to combat the "my script/program deletes the file/directory then tries to recreate it - why isn't the file/directory deleted when unlink() returns?" issue. Larry Hall lhall AT rfk DOT com RFK Partners, Inc. http://www.rfk.com 838 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/