Problems with native Unix domain sockets on Win 10/2019

Ken Brown kbrown@cornell.edu
Mon Feb 8 15:30:56 GMT 2021


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


More information about the Cygwin mailing list