rm fails but returns success

[Corinna Vinschen]

On Feb  3 17:02, Peter Rosin wrote:
> Hi!
> 
> I have this annoying leftover file from a automake testsuite run.
> I don't know if it was created by an MSYS process or a Cygwin
> process, but I can't get rid of it.  I can't take ownership of
> it either, not even as admin.  I haven't tried stopping all
> MSYS/Cygwin processes yet, nor rebooting, but I'd rather not.
> 
> Any help with that is appreciated.  No, not rebooting :-)
> 
> However, that is not really why I'm writing, I'm writing to
> report the following bug related to the above file.
> 
> $ uname -a
> CYGWIN_NT-6.1-WOW64 peda-pc 1.7.10s(0.259/5/3) 20120123 00:15:09 i686 Cygwin
> $ ls -l aclibobj.log-t
> -rw-r----- 1 ???????? ???????? 2113 Jan 31 16:09 aclibobj.log-t
> $ rm aclibobj.log-t; echo $?
> rm: remove write-protected regular file `aclibobj.log-t'? yes
> 0

Send an strace of this, please.  One reason that rm (better: unlink(2))
reports success is if the file is still in use by another process but
it's already marked as "delete pending" in the OS.  This should only
occur if a non-Cygwin process is still holding a handle to the file.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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