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