This is the mail archive of the
mailing list for the Cygwin project.
Re: umask not working?
- From: Andrey Repin <anrdaemon at yandex dot ru>
- To: Achim Gratz <Stromeko at nexgo dot de>, cygwin at cygwin dot com
- Date: Thu, 22 Mar 2018 01:57:51 +0300
- Subject: Re: umask not working?
- References: <email@example.com> <firstname.lastname@example.org> <E51C5B015DBD1348A1D85763337FB6D90189B91D4F@Remus.metastack.local> <87bmfhfepm.fsf@Rainer.invalid>
- Reply-to: cygwin at cygwin dot com
Greetings, Achim Gratz!
> 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,
Not so much a red herring, but it was mentioned in the reply to the specific
issue, also because of how Windows actually implemented access control, which
is much more sane than simple POSIX permissions.
> 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.
With best regards,
Thursday, March 22, 2018 01:09:01
Sorry for my terrible english...
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple