DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=wFIz7z9x1eUQrMKXnwnaXF3suTwxCn6iNvh+zX0i+e1UHovYZzNoV
	3whZ+jMYRIEk6mZoe44BqgywlyUOd+ipKtzOrzG6rYJtMWE8zkZZ0Y+13tFnFHqe
	WJWWydBqFPCCxMwfJMiAyr7ktkGBeSR0vVb2UtdRl3U+I2BvdeVV7Y=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Fri, 25 Apr 2014 14:16:14 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: rm -f behavior
Message-ID: <20140425121614.GB5666@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <5358260B.90807@obj-sys.com> <20140424142304.GT2339@calimero.vinschen.de> <53592F15.4040309@obj-sys.com> <20140424163624.GU2339@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="CdrF4e02JqNVZeln"
Content-Disposition: inline
In-Reply-To: <20140424163624.GU2339@calimero.vinschen.de>
User-Agent: Mutt/1.5.21 (2010-09-15)

--CdrF4e02JqNVZeln
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Apr 24 18:36, Corinna Vinschen wrote:
> On Apr 24 11:34, Douglas Coup wrote:
> > If I do "which rm" and "which chmod", it shows that both commands
> > resolve to the Cygwin binaries.
> >=20
> > The attached rm.notworking.trace file is from an "rm -f dac.txt"
> > command that gets the permission denied error; i.e., when the
> > permissions on the file are 444.  Things seem to start going south
> > at entry 34276.
>=20
> Gosh, how many ways to fail does transactional NTFS know?

Btw., this is not just the result of creating the file and chmod'ing it
to 444 in Cygwin, is it?  The reason I'm asking is that Cygwin does not
set the DOS R/O bit when chmod'ing the file to 444.  In fact, Cygwin
never sets the R/O bit, except for *.lnk type symlinks.

However, this:

> >    20   34002 [main] rm 7580 unlink_nt: Trying to delete \??\C:\mydocs\=
temp\dac.txt, isdir =3D 0
> >   274   34276 [main] rm 7580 unlink_nt: Opening \??\C:\mydocs\temp\dac.=
txt for removing R/O failed, status =3D 0xC0190052

shows that the DOS R/O bit was set.  If this attribute really showed up
after you'd called chmod, how did it get there?!?


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--CdrF4e02JqNVZeln
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJTWlIOAAoJEPU2Bp2uRE+gcSUP/0s1cFwwMWD5RNZSY4E8k2qe
0+tPtUWmyEenYtshE2PIQS165SfvHEhOlMkRv+tczjdpg6ddsCHbenPG8wanbW8T
26iOKwJYRkRavXHB/UXII6LQKFwZ9NE092O4Dt+yudPWfZ/q3sRcOw22Ot33DYw9
6m3s+7MYiU5VHh2MR/y1HSb5qqDg78bomH90A35Tw9i1qxA3dHirYyR5gFjZ6Ah8
4E1ZCCffA+/c2MmJa26eUv983FH0aQ9pMZLvaaUIYv49OL98byhOnabzFzODN8yI
HCQpfc7QMQFB2hQJipRTcwHnMjg72/hjtYUUwDzkWMWySiNFNTfp+BQgGDSgY7cm
ofvqex+GRRdFb7uSA9LxJakQWCtK9L41YjhIuhlnYJNEa5t0aeYYACAZmRAFzqWZ
v6GWLFxsdxifBV96NzLgkhmRktmMiVuQjgteJVApL4aoDbFAf3d/sRkdJto6Q/32
r2MrJFk3KSBC1p/DoaBk/tM9Y+d+WExFSp0IQ3yDrUqQN081ph1+W+hj+bhX+pz0
B118hXI2c3ud1tlsNSGd8Qql55UogmhqY08gHCSMv1LHxT7UOzMQ0rphKDB7B093
RN8NhFCzJnLuhtNNAZqKSC/FJM94Z7SGgzbtf+CLkNzVUuAhNrT1ha5TiwYHHg2D
AN2VIIn1vkI6Gsx52gGP
=WVll
-----END PGP SIGNATURE-----

--CdrF4e02JqNVZeln--