rm -f behavior

Corinna Vinschen corinna-cygwin@cygwin.com
Fri Apr 25 15:57:00 GMT 2014

On Apr 25 17:47, Corinna Vinschen wrote:
> On Apr 25 11:30, Douglas Coup wrote:
> > Incidentally, the sequence below should have nothing to do with Perforce.
> > 
> > $ touch dac.txt
> > $ chmod 444 dac.txt
> > $ rm -f dac.txt
> > 
> > This is being done completely outside of any Perforce workspaces.
> Sorry, this isn't helpful.  Make sure you're *really* using the correct
> Cygwin DLL from the snapshot (uname -a), and if the above sequence
> really fails to work, first call `attrib dac.txt' before calling rm to
> see if the R/O attribute is set, then call rm under strace again and
> send the strace.  Also, if the R/O attribute gets set in the above
> sequence, I have to know where it comes from.  As I said, Cygwin does
> not set the flag at all for normal files, not even in chmod.

...on NTFS.  It uses the R/O bit on FAT or other crippled filesystems,
but then it wouldn't even try to start a transaction since only NTFS
supports that anyway.


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://cygwin.com/pipermail/cygwin/attachments/20140425/dc4953fd/attachment.sig>

More information about the Cygwin mailing list