X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 	tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <5520d94f0901131502ke357789xe35873fba60f1822@mail.gmail.com>
Date: Tue, 13 Jan 2009 15:02:58 -0800
From: "greenup greenup" <greenup AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: rm seems to fail
In-Reply-To: <2ca21dcc0901131446x1c5d0993u7d6b59560cee3b1@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <5520d94f0901130852l310a9dfdk9821c26458d8d5e AT mail DOT gmail DOT com> 	 <5520d94f0901130901y66a7df50yca7e586998a3bea3 AT mail DOT gmail DOT com> 	 <5520d94f0901130916l7669d8capa39587365237da4f AT mail DOT gmail DOT com> 	 <f60fe000901131024q5a600fc0haa6e076196c98b1e AT mail DOT gmail DOT com> 	 <5520d94f0901131057o3cbb3915h95b824942d95be6c AT mail DOT gmail DOT com> 	 <f60fe000901131132q20944860k42863c1391a371d4 AT mail DOT gmail DOT com> 	 <5520d94f0901131152u3a3f8ae3y64654d175b5b37a4 AT mail DOT gmail DOT com> 	 <f60fe000901131207g571d0e34h72a3296142736faf AT mail DOT gmail DOT com> 	 <5520d94f0901131420m969107blcbf99559be75b1ca AT mail DOT gmail DOT com> 	 <2ca21dcc0901131446x1c5d0993u7d6b59560cee3b1 AT mail DOT gmail DOT com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

On 1/13/09, Dave Korn wrote:
> greenup greenup wrote:
>  > On 1/13/09, Mark J. Reed wrote:
>  >> On Tue, Jan 13, 2009 at 2:52 PM, greenup wrote:
>  >>  > your perl test was a nice try; but it also did not remove the file,
>  >>  > which is revealing.
>  >> I should have included a return code check:
>  >>  perl -e 'unlink("goo/foo") or die $!'
>  > I really want to know the root cause, so I'm re-upgrading my cygwin
>  > dll and coreutils, seeing if the dll was hiding, or some other cause
>   What AV have you got?  Sometimes your AV can keep a handle open to a file
>  (for scanning) for some time after you've last accessed it.  If you're trying
>  to delete it in that window (and this could happen every time automatically if
>  'rm' does a stat() to check the file exists and is readable right before
>  calling unlink()), then it might fail because it's in use.  Maybe your AV was
>  doing that for a while and now it's stopped.... but this is pretty speculative.

you know, I'm up for speculation right now.  Even before I got to
re-upgrade, it stopped succeeding.  I'm back to rm failing, and other
than opening/closing some terminal windows, I don't think I've done
anything.  In one window recently I nuked my path to only /usr/bin and
tested, just incase something else was being seen.

This machine uses Mcaffee OAS.  And it appears I don't have the power
to disable it even to test.  Mixed feelings about that... there are
some users that would leave it off a lot...

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/