Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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:	<3E2D33FA.5090200@polyspace.com>
Date:	Tue, 21 Jan 2003 12:50:18 +0100
From:	Gael Mulat <Gael DOT Mulat AT polyspace DOT com>
Organization:	PolySpace Technologies
User-Agent:	Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920 Netscape/7.0
X-Accept-Language:	en-us, en, fr-fr
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Bug in rm -r with locked files

    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/

- Raw text -