From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Problems with native Unix domain sockets on Win 10/2019
Date: Mon, 8 Feb 2021 10:30:56 -0500 [thread overview]
Message-ID: <7fb70a75-8557-6c95-27fa-697c92dcedce@cornell.edu> (raw)
In-Reply-To: <f46a8b81-5e5c-f84e-522c-fc322ffb6bdf@oracle.com>
On 2/7/2021 2:35 PM, Michael McMahon via Cygwin wrote:
> Hi Ken, Corinna
>
> Sorry for the delay in responding. I have just tested the fix and it works
> great. Thank you very much for looking into it.
>
> When do you think it would be available in a form that regular users would be
> able to update/install?
Corinna decides when to make a new Cygwin release. My best guess is "pretty soon".
> Also, one observation FYI, is that the "ls -l" command on Unix normally
> indicates sockets with an "s" as the first character of the output: eg
>
> srwxr-xr-x 1 Michael None 0 Feb 7 11:19 foo.sock
>
> Currently, what is shown on Cygwin is
>
> -rwxr-xr-x 1 Michael None 0 Feb 7 11:19 foo.sock
>
> indicating a regular file.
Right. From Cygwin's point of view, it is a regular file. There might come a
time when Cygwin's AF_UNIX implementation makes use of native Windows AF_UNIX
sockets on systems that support them. But that time is not currently in sight.
Ken
next prev parent reply other threads:[~2021-02-08 15:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 11:25 Michael McMahon
2020-09-24 11:26 ` Ken Brown
2020-09-24 12:01 ` Michael McMahon
2020-09-24 17:11 ` Brian Inglis
2020-09-25 13:19 ` Ken Brown
2020-09-25 14:29 ` Michael McMahon
2020-09-25 14:37 ` Eliot Moss
2020-09-25 16:13 ` Michael McMahon
2020-09-25 16:32 ` Eliot Moss
2020-09-25 18:50 ` Ken Brown
2020-09-25 20:30 ` Ken Brown
2020-09-26 0:31 ` Duncan Roe
2020-09-26 1:22 ` Ken Brown
2020-09-26 7:30 ` Michael McMahon
2020-09-28 11:03 ` Michael McMahon
2021-01-30 16:00 ` Ken Brown
2021-01-31 23:30 ` Michael McMahon
2021-02-01 15:04 ` Ken Brown
2021-02-01 15:10 ` Corinna Vinschen
2021-02-07 19:35 ` Michael McMahon
2021-02-08 15:30 ` Ken Brown [this message]
2021-03-16 11:06 ` Sv: " sten.kristian.ivarsson
2021-03-16 13:00 ` Michael McMahon
2021-03-16 15:19 ` Ken Brown
2021-03-17 12:47 ` Sv: " sten.kristian.ivarsson
2021-03-17 15:47 ` 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=7fb70a75-8557-6c95-27fa-697c92dcedce@cornell.edu \
--to=kbrown@cornell.edu \
--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).