From: Douglas Coup <dcoup@obj-sys.com>
To: cygwin@cygwin.com
Subject: rm -f behavior
Date: Wed, 23 Apr 2014 20:43:00 -0000 [thread overview]
Message-ID: <5358260B.90807@obj-sys.com> (raw)
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?
--
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
--
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
next reply other threads:[~2014-04-23 20:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 20:43 Douglas Coup [this message]
2014-04-24 14:23 ` Corinna Vinschen
2014-04-24 15:35 ` Douglas Coup
2014-04-24 16:36 ` Corinna Vinschen
2014-04-24 16:45 ` Corinna Vinschen
2014-04-24 17:10 ` Douglas Coup
2014-04-25 12:16 ` Corinna Vinschen
2014-04-25 14:23 ` Douglas Coup
2014-04-25 14:50 ` Corinna Vinschen
2014-04-25 15:30 ` Douglas Coup
2014-04-25 15:47 ` Corinna Vinschen
2014-04-25 15:57 ` Corinna Vinschen
2014-04-25 18:12 ` Douglas Coup
2014-04-25 19:16 ` Corinna Vinschen
2014-04-25 19:52 ` Douglas Coup
2014-04-25 19:59 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5358260B.90807@obj-sys.com \
--to=dcoup@obj-sys.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).