From: Michael McMahon <michael.x.mcmahon@oracle.com>
To: sten.kristian.ivarsson@gmail.com, cygwin@cygwin.com
Subject: Re: Sv: Problems with native Unix domain sockets on Win 10/2019
Date: Tue, 16 Mar 2021 13:00:30 +0000 [thread overview]
Message-ID: <c06b5537-b1f9-5ae7-fd85-8701c412239c@oracle.com> (raw)
In-Reply-To: <000201d71a54$638c67c0$2aa53740$@gmail.com>
I think you can download pre-released builds from:
https://cygwin.com/snapshots/
As mentioned already, the fix here is not actually support of AF_UNIX
sockets natively. My understanding is that they are implemented over
loopback TCP in cygwin, but the fix allows native AF_UNIX sockets to be
handled (eg deleted) as regular files through regular cygwin commands.
Michael.
On 16/03/2021 11:06, Kristian Ivarsson via Cygwin wrote:
> Hi all
>
> Does anyone know the status of these fixes ?
>
> I saw an announcement for cygwin-3.2.0-0.1 that seemed to contain some
> AF_UNIX-related fixes but I fail to find out where that distribution exists
> (if it is supposed to be publicly accessible?), but I tried out the
> 2021-03-01 snapshot and perhaps they are similar ?
>
> We bumped into some AF_UNIX-related issues when trying the 2021-03-01
> -snapshot though. It might be some flaws in our code base but the same code
> works in quite a few Linux-distros
>
> We're more than willing to help out with testing this and/or trying to
> narrow down any possible cygwin issues, but first we'd be glad if someone
> could give us some kind of status report of this (so no one is doing any
> unnecessary work)
>
>
> Best regards,
> Kristian
>
> p.s.
> I tried to build the topic/af_unix -branch according to the FAQ, but
> there was some issues
> d.s.
>
>
>
>>> 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
>> --
>> Problem reports: https://urldefense.com/v3/__https://cygwin.com/problems.html__;!!GqivPVa7Brio!OrhjUwBgvLe4_I38uHpiucq3-_xiQDxazv5s7XuBkOmzXTgGhz9Vb3GrB2RYCJM8jmPtbA$
>> FAQ: https://urldefense.com/v3/__https://cygwin.com/faq/__;!!GqivPVa7Brio!OrhjUwBgvLe4_I38uHpiucq3-_xiQDxazv5s7XuBkOmzXTgGhz9Vb3GrB2RYCJMQE63Mlg$
>> Documentation: https://urldefense.com/v3/__https://cygwin.com/docs.html__;!!GqivPVa7Brio!OrhjUwBgvLe4_I38uHpiucq3-_xiQDxazv5s7XuBkOmzXTgGhz9Vb3GrB2RYCJMRgFcrHA$
>> Unsubscribe info: https://urldefense.com/v3/__https://cygwin.com/ml/*unsubscribe-simple__;Iw!!GqivPVa7Brio!OrhjUwBgvLe4_I38uHpiucq3-_xiQDxazv5s7XuBkOmzXTgGhz9Vb3GrB2RYCJPOK0x2gw$
> --
> Problem reports: https://urldefense.com/v3/__https://cygwin.com/problems.html__;!!GqivPVa7Brio!OrhjUwBgvLe4_I38uHpiucq3-_xiQDxazv5s7XuBkOmzXTgGhz9Vb3GrB2RYCJM8jmPtbA$
> FAQ: https://urldefense.com/v3/__https://cygwin.com/faq/__;!!GqivPVa7Brio!OrhjUwBgvLe4_I38uHpiucq3-_xiQDxazv5s7XuBkOmzXTgGhz9Vb3GrB2RYCJMQE63Mlg$
> Documentation: https://urldefense.com/v3/__https://cygwin.com/docs.html__;!!GqivPVa7Brio!OrhjUwBgvLe4_I38uHpiucq3-_xiQDxazv5s7XuBkOmzXTgGhz9Vb3GrB2RYCJMRgFcrHA$
> Unsubscribe info: https://urldefense.com/v3/__https://cygwin.com/ml/*unsubscribe-simple__;Iw!!GqivPVa7Brio!OrhjUwBgvLe4_I38uHpiucq3-_xiQDxazv5s7XuBkOmzXTgGhz9Vb3GrB2RYCJPOK0x2gw$
next prev parent reply other threads:[~2021-03-16 13:00 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
2021-03-16 11:06 ` Sv: " sten.kristian.ivarsson
2021-03-16 13:00 ` Michael McMahon [this message]
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=c06b5537-b1f9-5ae7-fd85-8701c412239c@oracle.com \
--to=michael.x.mcmahon@oracle.com \
--cc=cygwin@cygwin.com \
--cc=sten.kristian.ivarsson@gmail.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).