public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Norton Allen <allen@huarp.harvard.edu>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Unix Domain Socket Limitation?
Date: Wed, 25 Nov 2020 16:47:16 -0500	[thread overview]
Message-ID: <71490665-31b0-f63c-74da-461a053fac21@huarp.harvard.edu> (raw)

In my recent tests, it appears as though it is not possible to 
successfully connect via two Unix Domain sockets from one client 
application to one server application.

Specifically, if I create a server which listens on a Unix Domain socket 
and a client, which attempts to connect() twice, both seem to lock up. 
This is not the behavior under Linux.

I will be happy to work up a minimal example if it is helpful in 
tracking this down. I wanted to start by asking whether this is a known 
limitation and/or if there is something about the Cygwin implementation 
that makes this sort of thing very difficult.



             reply	other threads:[~2020-11-25 21:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-25 21:47 Norton Allen [this message]
2020-11-25 22:27 ` Ken Brown
     [not found]   ` <4260ad1b-4ab2-fa36-fd0e-7c9644560114@huarp.harvard.edu>
2020-11-26 17:13     ` Ken Brown
2020-11-30 17:19       ` Norton Allen
2020-11-30 18:14         ` Ken Brown
2020-11-30 18:26           ` Norton Allen
2020-11-30 23:19             ` Ken Brown
2020-12-01  2:14               ` Norton Allen
2020-12-01  2:22                 ` Norton Allen
2020-12-02 17:30                   ` Norton Allen
2020-12-04  1:11                     ` Ken Brown
2020-12-04 13:51                       ` Norton Allen
2020-12-05 23:52                         ` Ken Brown
2020-12-06 17:17                           ` Norton Allen
2020-12-06 22:32                             ` 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=71490665-31b0-f63c-74da-461a053fac21@huarp.harvard.edu \
    --to=allen@huarp.harvard.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).