From: Ronald Otto Valentin Fischer <ashi.niwatori@the-quickest.com>
To: Ken Brown <kbrown@cornell.edu>, cygwin@cygwin.com
Subject: Re: Editors set x-bit (sometimes)
Date: Tue, 13 Dec 2016 15:20:00 -0000 [thread overview]
Message-ID: <1481642417.99199.817613057.617EE00F@webmail.messagingengine.com> (raw)
In-Reply-To: <7bbc7866-32f9-1c22-c39e-e7cc92e28222@cornell.edu>
> Does this help?
>
> https://cygwin.com/faq/faq.html#faq.using.same-with-permissions
While interesting, it seems to describe a different phenomenon.
Actually, when I create files by Cygwin tools only (touch, nano, ....),
the access rights are always correct. Indeed, even after removing the
extended ACL entries - as was suggested in the FAQ -, the problem still
appears.
However, I have a new finding: When I create a file from a CMD.EXE
command line, by i.e.
echo xx > abc.rb
the access rights *do* have the x-bits set! This is reproducible, but
only when the file which was created, is below my Cygwin tree! I agree
that this smells a lot like an extended ACL issue, but as I said,
setacl -b provided no help.
Ronald
--
Ronald Fischer <ronald.fischer@fusshuhn.de>
http://www.fusshuhn.de/
--
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 prev parent reply other threads:[~2016-12-13 15:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 10:39 Ronald Fischer
2016-12-13 13:54 ` Ken Brown
2016-12-13 15:20 ` Ronald Otto Valentin Fischer [this message]
2016-12-13 19:03 ` Brian Inglis
2016-12-13 19:47 ` Achim Gratz
2016-12-13 20:15 ` Henry S. Thompson
2016-12-14 13:37 ` Nellis, Kenneth
2016-12-14 17:35 ` Andrey Repin
2016-12-14 18:23 ` Achim Gratz
2016-12-14 20:28 ` Nellis, Kenneth
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=1481642417.99199.817613057.617EE00F@webmail.messagingengine.com \
--to=ashi.niwatori@the-quickest.com \
--cc=cygwin@cygwin.com \
--cc=kbrown@cornell.edu \
/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).