X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-0.9 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD
X-Spam-Check-By:	sourceware.org
Date:	Fri, 10 Sep 2010 10:48:30 -0700
From:	Quanah Gibson-Mount <quanah AT zimbra DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Oddities with file deletion on CIFS drive
Message-ID:	<1830BEA90D9D88BCE0394504@[192.168.1.2]>
MIME-Version:	1.0
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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 Friday, September 10, 2010 7:09 PM +0200 Corinna Vinschen wrote:

>> Let me know if there is anything else I can provide.
>
> I'm not sure.  I don't think so.  The problem is that the unlink(2)
> function in Cygwin does not get any error code from any of the OS
> functions it calls.  So, from the Cygwin POV everything worked fine.
> How is it supposed to know that anything has gone wrong, if the
> underlying OS doesn't tell?

Heh, magic I guess.  If I mount the drive as a CIFS drive from a Linux box,
I can delete the files just fine, so for now that gives me a workaround
(I'll move my deletion process to a Linux box).

--Quanah

--

Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra ::  the leader in open source messaging and collaboration
Zimbra ::  the leader in open source messaging and collaboration

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

- Raw text -