This is the mail archive of the
mailing list for the Cygwin project.
Re: umask not working?
- From: Brian Inglis <Brian dot Inglis at SystematicSw dot ab dot ca>
- To: cygwin at cygwin dot com
- Date: Wed, 21 Mar 2018 13:20:35 -0600
- Subject: Re: umask not working?
- References: <firstname.lastname@example.org> <email@example.com> <E51C5B015DBD1348A1D85763337FB6D90189B91D4F@Remus.metastack.local> <87bmfhfepm.fsf@Rainer.invalid>
- Reply-to: Brian dot Inglis at SystematicSw dot ab dot ca
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
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple