Re: permission 600

[Tatsuro MATSUOKA <tmacchant2@yahoo.co.jp>]

> ----- Original Message -----
> 
> From: "Thomas Wolff" 
> Date: 2022/01/09 日 17:51
> Subject: Re: permission 600
> 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?

I made another windows account and sign in PC with different user name.
But result for chmod 600 gave the same results.
I found the workaround for jupyter by readind the code of "paths.py" in jupyter.

Tatsuro