From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 126164 invoked by alias); 13 Dec 2016 15:20:30 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 126141 invoked by uid 89); 13 Dec 2016 15:20:29 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=H*MI:sk:7bbc786, H*f:sk:7bbc786, H*i:sk:7bbc786, HTo:U*kbrown X-HELO: out1-smtp.messagingengine.com Received: from out1-smtp.messagingengine.com (HELO out1-smtp.messagingengine.com) (66.111.4.25) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 13 Dec 2016 15:20:19 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 1341220782; Tue, 13 Dec 2016 10:20:18 -0500 (EST) Received: from web1 ([10.202.2.211]) by compute1.internal (MEProxy); Tue, 13 Dec 2016 10:20:18 -0500 X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id DBCA6AA6C0; Tue, 13 Dec 2016 10:20:17 -0500 (EST) Message-Id: <1481642417.99199.817613057.617EE00F@webmail.messagingengine.com> From: Ronald Otto Valentin Fischer To: Ken Brown , cygwin@cygwin.com MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" References: <1481625566.176738.817340945.718D9CF0@webmail.messagingengine.com> <7bbc7866-32f9-1c22-c39e-e7cc92e28222@cornell.edu> Subject: Re: Editors set x-bit (sometimes) Date: Tue, 13 Dec 2016 15:20:00 -0000 In-Reply-To: <7bbc7866-32f9-1c22-c39e-e7cc92e28222@cornell.edu> X-SW-Source: 2016-12/txt/msg00130.txt.bz2 > 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 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