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: <00b701c2c1af$a0fe8eb0$3300a8c0@nakagami> From: "Carlo Florendo" To: Subject: Re: Bug in rm -r with locked files Date: Wed, 22 Jan 2003 09:45:56 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300 What cygwin, vi, and fileutils versions are you using? In my case, I simulated the test case but rm returned immediately with rm: cannot remove `/tmp/direx/a.swp': Permission denied rm: cannot remove directory `/tmp/direx': Directory not empty I'm using vim 5.8.9, fileutils 4.1, and cygwin 1.3.15-1 Regards, Carlo -------------------- Carlo Florendo Astra Philippines Inc. email: carlo AT astra DOT ph URL: http://www.astra.ph ----- Original Message ----- From: David Means To: Gael Mulat Cc: cygwin AT cygwin DOT com Sent: Tuesday, January 21, 2003 9:35 PM Subject: Re: Bug in rm -r with locked files Yep, I concur. If windows has a lock on the file, rm just hangs. I've seen it hang on directories when doing an 'rm -rf yada/*" On Tue, 2003-01-21 at 06:50, Gael Mulat wrote: Hi, This is a bug report about rm (package fileutils, version 4.1-1) on W2K. Test case: take 2 cygwin shells. shell 1: mkdir /tmp/directory vi /tmp/directory/file shell 2: /bin/rm -rf /tmp/directory The shell2 doesn't manage to remove the directory and goes into an infinite loop, taking 100% of the CPU. All is then OK if we go out of vi in the shell1. Doing the same thing (deleting the directory) directly in Windows produces an error message: "cannot delete directory: Access is denied. The source file may be in use" and we can notice in the directory a file named .file.swp that is also visible under Cygwin with ls -la. The example I have just given uses vi, but it is the same with all processes that open the file, as W2K puts a lock on it. Gael Mulat -- 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/