X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 849873AAA04A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1624028636; bh=rtknOvWyL3WSJGoj/gPb64rcfgf0Mheyi1zhioiMaC0=; h=To:Subject:Date:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:From:Reply-To:From; b=Xb5cCvhj6EqbKdt91KJW8NoqHohY9UtufhMFkpjUe1DCv8RSCvvz7SoDjAK/ydp6Y fJ0yHbhrxpXVm/GvfPF7NAQbPqks/Cjd+YFSJZU0kn9zcMpERGKHf97COjQ0RsMkAf oqe4v2yAy0GR8u9s7O297VOmUYExv1Am+4Vd0efE= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org C5AA53AA9C7D X-Quarantine-ID: X-Virus-Scanned: Debian amavisd-new at mta02.prd.rdg.aluminati.org To: cygwin AT cygwin DOT com Subject: Files and Directories created by cygwin utilities do not have inheritance on Message-ID: Date: Fri, 18 Jun 2021 11:02:09 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 Content-Language: en-US X-Spam-Status: No, score=-3.1 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, JMQ_SPF_NEUTRAL, RCVD_IN_DNSWL_LOW, SPF_HELO_PASS, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 List-Id: General Cygwin discussions and problem reports List-Archive: List-Post: List-Help: List-Subscribe: , From: Rob Stevens via Cygwin Reply-To: Rob Stevens Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "Cygwin" Whenever I create a new file or directory using a cygwin utility, that object does not have the property that it inherits ACLs from its container. This appears to be true whether or not the noacl mount flag is on it the fstab. By contrast, using a windows utility (eg notepad or explorer) to create a new file/directory does have that property set on the newly created object, even when the new object is created under the cygwin top level directory. Why is this? Is it not important to propagate changes to the ACLs from the top level user directory? -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple