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:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=OddwUXzcti6+jWnztE0SJNhcx5yHn
	ORd5ud7IZz4HIogoRAdTSR8KZ4Gum3KnkogSmCDO8Irk6niYkoKz6FgDGUTB0oKu
	5LUkd+c2eBXfXdxxMtRTMwWuLdZqu7vnRuQ8u8y4z+xYG6NuuXCZucua4RWbiArO
	OLMD0MAywUNSi8=
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:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; s=default; bh=tpb3FF0jZDsC+4UGASNn+H/3Xak=; b=eYF
	2iLoCc1qruzkOOvmGkh4RsIv6HOGlqCSbPi4/h6A8pR2W+lMZ5eQv8PRqq18tj2t
	icbn6s+RyQv3ts/B8jYP8Jb/0TBLAY4GgUEIWuJpy0KnSZpWVIk+dYfFmAM95jsV
	ldD39B/oFDyuy4gqkcHuutuc8IC0QJRyupoMziCE=
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.6 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=H*M:local, HAccept-Language:en-GB
X-HELO: outmail148113.authsmtp.com
From: David Allsopp <David DOT Allsopp AT cl DOT cam DOT ac DOT uk>
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: RE: umask not working?
Date: Wed, 21 Mar 2018 10:27:57 +0000
Message-ID: <E51C5B015DBD1348A1D85763337FB6D90189B91D4F@Remus.metastack.local>
References: <000f01d3bf80$a2e0d8c0$e8a28a40$@cl.cam.ac.uk> <1941712084 DOT 20180319200734 AT yandex DOT ru>
In-Reply-To: <1941712084.20180319200734@yandex.ru>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
X-Server-Quench: 876aa844-2cf2-11e8-9f3c-9cb654bb2504
X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse
X-AuthRoute: OCd1ZAARAlZ5RRob BmUtCCtbTh09DhZI RxQKKE1TKxwUVhJa I0lFL1x7O0wTWlBf HTVUBhpWUUIMCCFq aQpQZRVcYkBMVw9q UAZLQ1FMFQVtHx4A BAAfUx1tdQBZeTA3 ZzoTPDcjWkRzckV+ RgBWFmQGK29nbjFO WERcagEHJgFXfx4Q Yk12AnBefGxUNHxl QwU5ZW1pYSNlBXYd XwQENlFaR0EXViE7 XRMDGzp4dQDY
X-Authentic-SMTP: 61633634383431.1039:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 213.105.212.114/25
X-AuthVirus-Status: No virus detected - but ensure you scan with your own anti-virus system.
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id w2LASEQn025302

Andrey Repin wrote:
> Greetings, David Allsopp!
> 
> > Is this expected behaviour:
> 
> > OPAM+DRA AT OPAM ~
> > $ uname -a ; umask ; touch /tmp/foo ; ls -l /tmp/foo ; mkdir /tmp/bar
> > ; touch /tmp/bar/foo ; ls -l /tmp/bar/foo CYGWIN_NT-6.1-WOW OPAM
> > 2.10.0(0.325/5/3) 2018-02-02 15:21 i686 Cygwin
> > 0022
> > -rw-r--r-- 1 OPAM+DRA OPAM+None 0 Mar 19 13:44 /tmp/foo
> > -rw-rw-r--+ 1 OPAM+DRA OPAM+None 0 Mar 19 13:44 /tmp/bar/foo
> 
> > Why does the file /tmp/bar/foo get g+w when /tmp/foo doesn't - I'm not
> > sure what to look at on my system to diagnose what I may have
> > inadvertently tweaked. The directory itself is:
> 
> > drwxr-xr-x+ 1 OPAM+DRA OPAM+None 0 Mar 19 13:44 /tmp/bar
> 
> Let me guess, /tmp usertemp ?

No - it's default mounts, so /tmp = C:\cygwin\tmp, to which my (non-administrative) user has write access. 

> 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? (In the actual scenario where I'm being bitten by this, it's because a git checkout is altering files which were 644 to be 664, so whether it's precisely umask or not, the *change* of permissions is the problem).


David


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