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: <5.1.0.14.2.20020406092736.0267b5a8@pop3.cris.com>
X-Sender: rrschulz AT pop3 DOT cris DOT com
Date: Sat, 06 Apr 2002 09:28:51 -0800
To: "Chris January" <chris AT atomice DOT net>, <cygwin AT cygwin DOT com>
From: Randall R Schulz <rrschulz AT cris DOT com>
Subject: Re: Infinite Loop In "rm -fr" When Busy File Encountered
In-Reply-To: <003801c1dd90$252f4ad0$0100a8c0@advent02>
References: <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020405195515 DOT 026fbb28 AT pop3 DOT cris DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

Chris,

At 09:26 2002-04-06, Chris January wrote:
> > Greetings,
> >
> > I have encountered a problem in "rm" when used with the "-f" and "-r"
> > options and a busy and hence unremovable file is encountered.
> >
> > When "rm -fr" encounters a busy and hence unremovable file, it goes into an
> > infinite loop consuming as much CPU time as it can get until it is forcibly
> > terminated. The error is completely repeatable as long as the file remains
> > busy by virtue of being open in another program.
> >
> > The file system is NTFS and the mount is binmode. The system is Windows
> > 2000 Pro with SP2 and security patches installed.
> >
> > This is an up-to-date Cygwin installation that is exhibiting no other
> > anomalous behavior.
> >
> > In reference to the attached "cygcheck -rs" output, this happened on "C:"
> > "/cygdrive/c" (reached via a symlink "/c -> /cygdrive/c").
>
>I tried exhaustively to reproduce this (cygwin1.dll v1.3.10), but failed.


"Exhaustively?" In such little time?

Please tell me what you tried. I believe when it happened to me the file 
triggering the problem was open for writing.

Randall Schulz


>Chris


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