From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: umask problem: wrong permissions for new files
Date: Fri, 20 Apr 2018 12:47:00 -0000 [thread overview]
Message-ID: <5cdf9901f2c50f2fa15d7ce5c01c8fdf@smtp-cloud7.xs4all.net> (raw)
In-Reply-To: <20180420100357.GA21217@rus.uni-stuttgart.de>
On Fri, 20 Apr 2018 12:03:57, 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?
They do.
64-@@ umask
0022
64-@@ ls -l /tmp
total 0
-rw-r--r-- 1 Henri None 0 Apr 20 14:37 junk
64-@@ touch /tmp/junk
64-@@ ls -l /tmp
total 0
-rw-r--r-- 1 Henri None 0 Apr 20 14:39 junk
64-@@ getfacl /tmp
# file: /tmp
# owner: Henri
# group: None
# flags: --t
user::rwx
group::rwx
other:rwx
default:user::rwx
default:group::r-x
default:other:r-x
64-@@ icacls e:/Cygwin64/tmp
e:/Cygwin64/tmp Seven\Henri:(F)
Seven\None:(RX,W)
Everyone:(RX,W)
NULL SID:(RD)
CREATOR OWNER:(OI)(CI)(IO)(F)
CREATOR GROUP:(OI)(CI)(IO)(RX)
Everyone:(OI)(CI)(IO)(RX)
Successfully processed 1 files; Failed processing 0 files
Remember, it is Windows ... So you have to work a little harder :-)
Henri
--
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
next prev parent reply other threads:[~2018-04-20 12:47 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 [this message]
2018-04-20 12:53 ` Houder
2018-04-20 13:07 ` Corinna Vinschen
2018-04-20 13:25 ` Brian Inglis
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=5cdf9901f2c50f2fa15d7ce5c01c8fdf@smtp-cloud7.xs4all.net \
--to=houder@xs4all.nl \
--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).