From: Ken Brown <kbrown@cornell.edu>
To: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr@ncbi.nlm.nih.gov>,
"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Weird issue with file permissions
Date: Fri, 1 Jul 2022 16:59:27 -0400 [thread overview]
Message-ID: <e03b9932-abbd-9cf0-8db6-eea3518aa443@cornell.edu> (raw)
In-Reply-To: <DM8PR09MB7095238F3C4EA53DAC7A4179A5BD9@DM8PR09MB7095.namprd09.prod.outlook.com>
On 7/1/2022 2:00 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
> Lastly, I forgot to list all the involved directories as they look from under Cygwin with their permissions,
> if that's of any help:
>
> $ ls -ld ~ ~/.socket ~/subdir ~/subdir/.socket
> drwx------+ 1 ANTON None 0 Jul 1 13:36 /home/ANTON/
> srw-rw-rw- 1 ANTON None 0 Jul 1 13:36 /home/ANTON/.socket=
> drwxr-xr-x+ 1 ANTON None 0 Jul 1 13:36 /home/ANTON/subdir/
> srw-rw-rw- 1 ANTON None 0 Jul 1 13:36 /home/ANTON/subdir/.socket=
>
> $ ls -ld /cygdrive/g/cygwin /cygdrive/g/cygwin/.socket /cygdrive/g/cygwin/subdir /cygdrive/g/cygwin/subdir/.socket /cygdrive/g/cygwin/subdir-cmd /cygdrive/g/cygwin/subdir-cmd/.socket
> drwxrwx---+ 1 ANTON None 0 Jul 1 13:40 /cygdrive/g/cygwin/
> srw-rw-rw-+ 1 ANTON None 0 Jul 1 13:39 /cygdrive/g/cygwin/.socket=
> drwxrwxr-x+ 1 ANTON None 0 Jul 1 13:39 /cygdrive/g/cygwin/subdir/
> srw-rw-r--+ 1 ANTON None 0 Jul 1 13:39 /cygdrive/g/cygwin/subdir/.socket=
> drwxrwx---+ 1 ANTON None 0 Jul 1 13:40 /cygdrive/g/cygwin/subdir-cmd/
> srw-rw-rw-+ 1 ANTON None 0 Jul 1 13:40 /cygdrive/g/cygwin/subdir-cmd/.socket=
I've got my patch ready but need to test it before submitting it. In the
meantime, I just noticed that all of the directories you've listed have
non-standard ACL entries (indicated by the + signs). getfacl should show you
what they are.
Cygwin does not do this on a standard installation. Is it something you've done
intentionally? If not, you might want to remove those non-standard entries and
see if that has any impact on the problems you've reported. The -b and -k
options to setfacl are useful here.
Ken
next prev parent reply other threads:[~2022-07-01 20:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 18:00 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-07-01 19:01 ` Ken Brown
2022-07-01 20:59 ` Ken Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-03 1:51 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-07-02 16:16 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-07-02 18:41 ` Ken Brown
2022-07-02 3:23 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-07-02 14:43 ` Ken Brown
2022-07-01 22:11 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-07-01 23:16 ` Ken Brown
2022-07-01 5:46 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-07-01 17:03 ` Ken Brown
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=e03b9932-abbd-9cf0-8db6-eea3518aa443@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
--cc=lavr@ncbi.nlm.nih.gov \
/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).