From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: chmod issue on 3.1.7.
Date: Sat, 10 Oct 2020 15:51:37 -0600 [thread overview]
Message-ID: <ff1ef183-acef-5b58-00d5-876188822725@SystematicSw.ab.ca> (raw)
In-Reply-To: <ef27ae60-ac04-a74b-3bed-a927788f6cf4@cornell.edu>
On 2020-10-10 13:41, Ken Brown via Cygwin wrote:
> On 10/10/2020 12:32 PM, Kaz Kylheku (Cygwin) via Cygwin wrote:
>> Hi all,
>>
>> Running this Cygwin on a Windows 10 system:
>>
>> 0:DESKTOP-K8055OB:~$ uname -a
>> CYGWIN_NT-10.0-WOW DESKTOP-K8055OB 3.1.7(0.340/5/3) 2020-08-22 19:03 i686
>> Cygwi
>>
>> When a file is created, and permissions set as follows:
>>
>> 0:DESKTOP-K8055OB:~$ touch tempfile
>> 0:DESKTOP-K8055OB:~$ chmod 03777 tempfile
>> 0:DESKTOP-K8055OB:~$ ls -l tempfile
>> -rwsrwsrwt 1 kaz kaz 0 Oct 10 08:59 tempfile
>>
>> Then "chmod u=" is not able to clear the owner's permissions to nothing:
>>
>> 0:DESKTOP-K8055OB:~$ chmod u= tempfile
>> 0:DESKTOP-K8055OB:~$ ls -l tempfile
>> -rwxrwsrwt 1 kaz kaz 0 Oct 10 08:59 tempfile
>>
>> As you can see, it has no effect. The expected value is ----rwsrwt.
>>
>> I tried both with 64 and 32 bit Cygwin: same deal.
>>
>> This is not a problem with the chmod utility. I ran into this as a failing
>> test case against a chmod library function in a programming language.
>>
>> http://www.kylheku.com/cgit/txr/tree/tests/018/chmod.tl
>>
>> The test cases pass until the "u=", which fails in the same way.
>> This does not use the chmod utility.
>>
>> It's an issue with the chmod system call.
>>
>> This used to work on my older Cygwin installation, which was around 2.5.
>
> FWIW, I can't reproduce this on my system:
>
> $ uname -a
> CYGWIN_NT-10.0-WOW XXX 3.1.7(0.340/5/3) 2020-08-22 19:03 i686 Cygwin
>
> $ touch tempfile
>
> $ ls -l tempfile
> -rw-r--r-- 1 kbrown None 0 2020-10-10 15:16 tempfile
>
> $ chmod 03777 tempfile
>
> $ ls -l tempfile
> -rwxrwsrwt 1 kbrown None 0 2020-10-10 15:16 tempfile
>
> $ chmod u= tempfile
>
> $ ls -l tempfile
> ----rwsrwt 1 kbrown None 0 2020-10-10 15:16 tempfile
D/ACLs on the directory could restore/maintain the permissions:
could we please see the output from ls -l, getfacl, and icacls on the directory
and file?
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2020-10-10 21:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-10 16:32 Kaz Kylheku (Cygwin)
2020-10-10 19:41 ` Ken Brown
2020-10-10 21:51 ` Brian Inglis [this message]
2020-10-11 16:13 ` Kaz Kylheku (Cygwin)
2020-12-24 21:13 ` Kaz Kylheku (Cygwin)
2020-12-24 22:56 ` Ken Brown
2020-12-25 9:15 Kaz Kylheku (Cygwin)
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=ff1ef183-acef-5b58-00d5-876188822725@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).