This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Bug in rm -r with locked files


Actually the tests I ran in response to this thread used the most current 
vim (6.1-2) and fileutils (4.1-1) with cygwin 1.3.17-1, 1.3.18-1, and the 
latest snapshot.  The versions you're using are out-of-date.  But I expect 
the main difference is in vim and some change there.  But perhaps you can 
help verify that by updating to cygwin 1.3.18-1 and rerunning the test.  
Then try again with the most current vim (6.1.-2).

Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX

At 07:45 PM 1/21/2003, Carlo Florendo wrote:
>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@astra.ph
>URL: http://www.astra.ph
>
>
>----- Original Message -----
>From: David Means
>To: Gael Mulat
>Cc: cygwin@cygwin.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/


--
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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]