public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: umask problem: wrong permissions for new files
Date: Fri, 20 Apr 2018 13:25:00 -0000	[thread overview]
Message-ID: <6cd38c2e-2271-aaee-3263-babf905325c1@SystematicSw.ab.ca> (raw)
In-Reply-To: <20180420100357.GA21217@rus.uni-stuttgart.de>

On 2018-04-20 04:03, Ulli Horlacher wrote:
> cygwin umask does not work as expected:
> /tmp: uname -a; umask; rm -f zz; touch zz; ls -l zz
> Linux diaspora 4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2 16:08:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
> 0022
> -rw-r--r-- 1 framstag users 0 Apr 20 12:00 zz
> /tmp: uname -a; umask; rm -f zz; touch zz; ls -l zz
> CYGWIN_NT-6.1 WIN-LS0QDOSDIBL 2.10.0(0.325/5/3) 2018-02-02 15:21 i686 Cygwin
> 0022
> -rw-rw----+ 1 admin None 0 Apr 20 12:00 zz
> Why do not have new files mode -rw-r--r-- on cygwin?

Cygwin supports Windows ACLs as POSIX ACLs, which are also supported by Linux.
Use setfacl to set similar default ACLs (DACLs) on a Linux directory, rerun your
test there, and you should see similar results.

*Never* remove DACLs from any Windows directory which will *ever* be used with
any non-Cygwin Windows program: /undefined behaviour/ will result.
Mostly neither Cygwin nor Windows programs will be able to do anything with
those files until you fix the permissions problems using elevated commands ;^>

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

  parent reply	other threads:[~2018-04-20 13:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-20 10:04 Ulli Horlacher
2018-04-20 12:47 ` Houder
2018-04-20 12:53   ` Houder
2018-04-20 13:07 ` Corinna Vinschen
2018-04-20 13:25 ` Brian Inglis [this message]
2018-04-26 14:38   ` Ulli Horlacher
2018-04-27  9:05     ` Andrey Repin
2018-04-27  9:27       ` Eliot Moss

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6cd38c2e-2271-aaee-3263-babf905325c1@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).