If I do "which rm" and "which chmod", it shows that both commands 
resolve to the Cygwin binaries.

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.

The attached rm.working.trace file is from an "rm -f dac.txt" command 
done after I do a "chmod u+w dac.txt" command.

Regards,

Doug Coup

Objective Systems, Inc.
REAL WORLD ASN.1 AND XML SOLUTIONS
Tel: +1 (484) 875-9841
Fax: +1 (484) 875-9830
Toll-free: (877) 307-6855 (USA only)
http://www.obj-sys.com

On 4/24/2014 10:23 AM, Corinna Vinschen wrote:
> On Apr 23 16:43, Douglas Coup wrote:
>> I run Cygwin on a Windows 8.1 workstation.
>>
>> I just recently started noticing that the following sequence doesn't work:
>>
>> $ touch dac.txt
>> $ chmod 444 dac.txt
>> $ rm -f dac.txt
>>
>> The rm -f command gets a permission denied error.  This just started
>> happening recently, and I'm thinking it's because of an update to
>> Windows.
>>
>> If I do chmod u+w dac.txt before the rm -f command, then the command works.
>>
>> The same sequence executed on a different machine that runs Windows
>> 7 and hasn't been updated in a while works fine.  And it used to
>> work fine on my workstation.
>>
>> Is anyone else seeing this behavior?
> Not me.  Are you sure you're using Cygwin's rm and chmod?
> Could this be related to parent directory permissions?
>
> The problem would be in Cygwin if that happens, but I tested this on a
> fully updated Windows 8.1 in 32 and 64 bit.
>
> Does an `strace -o rm.trace rm dac.txt' give a clue in rm.trace?
>
>
> Corinna
>