X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=oCCyni8UdtFgjkdG
	w7kOuGlUQ6AYOd4RIcY1Fz379sCvWC/cN94E/r4omfMZlleCA/i0cPMBpmGJy32Y
	adOlXyBnjRFwo4TxLCb7TQwv4vbVJqpI9HB8qvzlKZDL7Ye8wO1eC1/gMktdPpMG
	qbwrHskiHIOt+Rx9GAB0TqSh1Jk=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=aEn3K169RyXPnrYu+t+ghk
	LonUE=; b=VBHwhjIpKnGCvqy536wEPlC2MHYKchBL28Da3bcP2olqfZLDCRbAXX
	YxkzCBHR3Goz75fekjq9+AVfjMj64wfZuwzhGQMftFuCV2Kx3hrKeKdE5qTUpz/e
	cwcMavXEyJ4Iu1PO85sKgT79lo1qWBNXg6dqvxi1+q2d0ZYoc6waA=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=calgary, Alberta, inglis, Inglis
X-HELO: smtp-out-no.shaw.ca
X-Authority-Analysis: v=2.3 cv=Tai4SyYh c=1 sm=1 tr=0 a=MVEHjbUiAHxQW0jfcDq5EA==:117 a=MVEHjbUiAHxQW0jfcDq5EA==:17 a=IkcTkHD0fZMA:10 a=SSIcQjt6Y_OVC1G7yHsA:9 a=QEXdDO2ut3YA:10
Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca
Subject: Re: umask not working?
To: cygwin AT cygwin DOT com
References: <000f01d3bf80$a2e0d8c0$e8a28a40$@cl.cam.ac.uk> <1941712084 DOT 20180319200734 AT yandex DOT ru> <E51C5B015DBD1348A1D85763337FB6D90189B91D4F AT Remus DOT metastack DOT local> <87bmfhfepm DOT fsf AT Rainer DOT invalid>
From: Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Message-ID: <3003fbe1-6bb0-5111-e0d9-a064b4801650@SystematicSw.ab.ca>
Date: Wed, 21 Mar 2018 13:20:35 -0600
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <87bmfhfepm.fsf@Rainer.invalid>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfFcMy3BXL6lEGQjliv0lgHREWEQJhmMH3THFCpSN1mJ+004sEyOlckKvAxRARxLZy6QIJZVQGbar9HhkMQ1751701gSaM2mIuO+MiAiGwKwGL2HWHI8x zvKR3GiY5GFO8peTY5XnfKwxgZIV5VrSh8OMky7PgrzabAe2AmmNFP5VmtmH62ZDWgN5LJcArhohvA==
X-IsSubscribed: yes

On 2018-03-21 12:47, Achim Gratz wrote:
> David Allsopp writes:
>>> You have extended ACL on the object. And overall, umask is not a good
>>> idea in Windows.
>>
>> "umask is not a good idea in Windows" - where's that come from?
> 
> Ask three people and get at least seven answers.
> 
> Actually Windows is a red herring IMHO, it's the combination of umask
> with DACL is the thing that doesn't mix well unless you keep it in a
> very tight box.  In your case, if you'd just remove the DACL from the
> directories your repo is in (and any files and directories below
> assuming that the ownership is the same for all of them) it'll probably
> immediately start working as you expect it to.  Depending on which
> volume the directory is actually on and what WIndows software tries to
> touch it you might find that some of these come back after a while, I
> generally avoid any system volume for that reason.

If users remove directory DACLs, they should never try to use any non-Cygwin
programs to create or use files in those directories: without DACLs, files
created by non-Cygwin programs will have no access permissions, and can not be
accessed by any programs without elevated admin rights.

To support the interoperability offered by Cygwin, most users should ensure that
Cygwin directory DACLs match the default umask, so that all programs can create,
use, and change files in those directories.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
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