From: Mark Geisert <mark@maxrnd.com>
To: cygwin@cygwin.com
Subject: Re: AW: RPC clnt_create() adress already in use
Date: Tue, 09 Jan 2018 04:55:00 -0000 [thread overview]
Message-ID: <9e5fb028-573e-b4cd-7a44-77be4f0fb306@maxrnd.com> (raw)
In-Reply-To: <59D90AF8D70E9740907BACDE2BCB520836CEAFA5@RESW102.resdom01.local>
Hi Raimund,
I think I might have an idea where the root cause is. But first I want to
revisit your very first email on this subject, from last September 22. You
mentioned test results from various Cygwin versions vs various Windows versions.
Are you absolutely sure your test program ran correctly on Cygwin 1.5.18 on
*both* Windows XP and Windows 7?
The reason I ask is that Windows' handling of socket option SO_REUSEADDR has
changed over time and Cygwin has had to make accommodations to keep up. There
might possibly be a need to revisit this within Cygwin.
I want to test a possible solution within the Cygwin DLL on my test machine but
it has another two days to go on a factorization problem it's running (under
Cygwin). So I will respond again after I test.
Thank you,
..mark
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-01-09 4:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 8:13 PAULUS, Raimund, TI-ABN
2018-01-09 4:55 ` Mark Geisert [this message]
2018-01-09 8:14 ` WG: " PAULUS, Raimund, TI-ABN
-- strict thread matches above, loose matches on Subject: below --
2017-12-30 18:39 PAULUS, Raimund, TI-ABN
2017-12-31 17:10 ` Mark Geisert
2017-09-25 6:19 PAULUS, Raimund, TI-ABN
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=9e5fb028-573e-b4cd-7a44-77be4f0fb306@maxrnd.com \
--to=mark@maxrnd.com \
--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).