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
Date: Tue, 21 Jan 2003 14:34:20 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Bug in rm -r with locked files
Message-ID: <20030121133420.GR29236@cygbert.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <3E2D33FA DOT 5090200 AT polyspace DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3E2D33FA.5090200@polyspace.com>
User-Agent: Mutt/1.4i

On Tue, Jan 21, 2003 at 12:50:18PM +0100, 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.

Which version of Cygwin and Vim are you using?  I'm getting this:

  shell 1:
     mkdir /tmp/foo
     vi /tmp/foo/bar
     :w                 <= To create file `bar'

  shell 2:
     rm -rf /tmp/foo    <= returns immediately, having foo removed.

Vim doesn't lock the file, so I wonder what you are discribing here.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

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