X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 	tests=BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <f60fe000901131207g571d0e34h72a3296142736faf@mail.gmail.com>
Date: Tue, 13 Jan 2009 15:07:55 -0500
From: "Mark J. Reed" <markjreed AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: rm seems to fail
In-Reply-To: <5520d94f0901131152u3a3f8ae3y64654d175b5b37a4@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
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>
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 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 suspect that will still run silently without removing the file,
indicating that the problem is indeed in the unlink(2) system call.
Which *should* succeed in any case; unlink() doesn't care about the
permissions of the target file, only of the directory containing it.

I see your original message confirmed that you were running Cygwin's
rm, btw; sorry for the extra hoop-jumping there.

So at this point I'm at a loss.  I'm running the same version of
Cygwin (though on Vista, not XP) on the same type of filesystem (NTFS)
and not seeing the issue.  Is there any way this could be
BLODA-induced?

 --
Mark J. Reed <markjreed AT gmail DOT com>

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