This is the mail archive of the
mailing list for the Cygwin project.
Re: umask not working?
- From: Achim Gratz <Stromeko at nexgo dot de>
- To: cygwin at cygwin dot com
- Date: Wed, 21 Mar 2018 19:47:33 +0100
- Subject: Re: umask not working?
- References: <email@example.com> <firstname.lastname@example.org> <E51C5B015DBD1348A1D85763337FB6D90189B91D4F@Remus.metastack.local>
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.
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf rackAttack V1.04R1:
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple