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:	<031901c2c181$0cfa08d0$78d96f83@pomello>
From:	"Max Bowsher" <maxb AT ukf DOT net>
To:	"Shankar Unni" <shankar AT cotagesoft DOT com>, <cygwin AT cygwin DOT com>
References:	<232810-220031221163510989 AT M2W098 DOT mail2web DOT com> <3E2D99F9 DOT 2040204 AT cotagesoft DOT com>
Subject:	Re: Bug in rm -r with locked files
Date:	Tue, 21 Jan 2003 19:12:32 -0000
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1106

Shankar Unni wrote:
> I don't think that was the primary issue.  The issue was that if a
> process is using a directory as its working directory (chdir()'ed into
> it), "rm -rf" goes into an infinite loop attempting to remove the
> directory (rather than print an error and move on).

No. The thing that rm -rf gets stuck on is vim .swp recovery file.

Max.


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