From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: permission 600
Date: Sun, 9 Jan 2022 09:51:14 +0100 [thread overview]
Message-ID: <0a2a4bff-fbf7-02c8-cf28-3a6271edaa6c@towo.net> (raw)
In-Reply-To: <517210150.1192809.1641708654835.JavaMail.yahoo@mail.yahoo.co.jp>
Am 09.01.2022 um 07:10 schrieb Tatsuro MATSUOKA:
>> ----- Original Message -----
>>
>> From: "Marco Atzeri"
>> To: "cygwin> Date: 2022/01/09 日 14:39
>> Subject: Re: permission 600
>>
>>
>> On 09.01.2022 06:28, Tatsuro MATSUOKA wrote:
>>> $ echo aaa > test.txt
>>> $ ls -l test.txt
>>> -rw-r--r-- 1 user user 4 Jan 9 14:07 test.txt
>>> $ chmod 600 test.txt
>>> $ ls -l test.txt
>>> -rw-r--r-- 1 user user 4 Jan 9 14:07 test.txt
>> it works for me
>>
>> $ ls -l test.txt
>> -rw-r--r-- 1 Marco Kein 4 Jan 9 06:35 test.txt
>>
>> $ chmod 600 test.txt
>>
>> $ ls -l test.txt
>> -rw------- 1 Marco Kein 4 Jan 9 06:35 test.txt
>>
>> I suspect that having user and group called same
>> is the clue
>>
> Ah! Thanks!
>
> Tatsuro
Did you verify it by using different names?
It can hardly be an explanation by POSIX means. If so, it must be some
weird consequence of Windows-specific stuff. Maybe a workaround could be
found for cygwin?
Thomas
next prev parent reply other threads:[~2022-01-09 8:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <517210150.1192809.1641708654835.JavaMail.yahoo.ref@mail.yahoo.co.jp>
2022-01-09 6:10 ` Tatsuro MATSUOKA
2022-01-09 8:51 ` Thomas Wolff [this message]
[not found] <1678276178.1336676.1641891339407.JavaMail.yahoo.ref@mail.yahoo.co.jp>
2022-01-11 8:55 ` Tatsuro MATSUOKA
[not found] <996962702.1253083.1641813036736.JavaMail.yahoo.ref@mail.yahoo.co.jp>
2022-01-10 11:10 ` Tatsuro MATSUOKA
[not found] <13484389.1228247.1641769990069.JavaMail.yahoo.ref@mail.yahoo.co.jp>
2022-01-09 23:13 ` Tatsuro MATSUOKA
2022-01-09 23:26 ` Thomas Wolff
[not found] <1804805239.1181531.1641726692666.JavaMail.yahoo.ref@mail.yahoo.co.jp>
2022-01-09 11:11 ` Tatsuro MATSUOKA
2022-01-09 11:25 ` Eliot Moss
[not found] <584156248.1199495.1641706088853.JavaMail.yahoo.ref@mail.yahoo.co.jp>
2022-01-09 5:28 ` Tatsuro MATSUOKA
2022-01-09 5:38 ` Marco Atzeri
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=0a2a4bff-fbf7-02c8-cf28-3a6271edaa6c@towo.net \
--to=towo@towo.net \
--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).