From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr@ncbi.nlm.nih.gov>
To: Ken Brown <kbrown@cornell.edu>, "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Weird issue with file permissions
Date: Sat, 2 Jul 2022 03:23:40 +0000 [thread overview]
Message-ID: <DM8PR09MB70951D58CC3208CB938D56B4A5BC9@DM8PR09MB7095.namprd09.prod.outlook.com> (raw)
> That way I'm sure I won't have any surprises with permissions when working in
> /cygdrive/g/cygwin. Do you want to try that and see if it makes a difference?
I have no problems with /cygdrive/g/cygwin -- my socket file gets created there with proper
permissions and reported so, too (both fstat and stat).
I have problems with the socket file that gets created under any subdirectory of that
directory IFF that subdirectory was created from under Cygwin (!) -- like with a shell command.
Creating the socket file in a subdirectory created by Windows works! Isn't that weird?
Anton Lavrentiev
Contractor NIH/NLM/NCBI
next reply other threads:[~2022-07-02 3:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-02 3:23 Lavrentiev, Anton (NIH/NLM/NCBI) [C] [this message]
2022-07-02 14:43 ` Ken Brown
-- 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-01 22:11 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-07-01 23:16 ` Ken Brown
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
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=DM8PR09MB70951D58CC3208CB938D56B4A5BC9@DM8PR09MB7095.namprd09.prod.outlook.com \
--to=lavr@ncbi.nlm.nih.gov \
--cc=cygwin@cygwin.com \
--cc=kbrown@cornell.edu \
/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).