From: Fedin Pavel <p.fedin@samsung.com>
To: cygwin@cygwin.com
Subject: Re: RPC inconsistency
Date: Mon, 14 May 2012 07:52:00 -0000 [thread overview]
Message-ID: <4FB0B9B0.10503@samsung.com> (raw)
In-Reply-To: <4FB09B1A.70004@samsung.com>
On 14.05.2012 9:41, Fedin Pavel wrote:
> 2. ti-rpc should come with more advanced port mapper (google told me
> it's named rpcbind). ti-rpc library can't work with old portmap.
After some more debugging...
1. In fact they should be interoperable. If UNIX socket fails, ti-rpc
library tries backwards-compatible method (IP socket on localhost).
2. For some reason it tries IPv6 socket, and, of course, fails. It
doesn't try IPv4 after this.
3. If i comment out IPv6 entries in /etc/netconfig, it will try IPv4 TCP
socket. But for some weird reason it fails to connect() with EADDRINUSE
error.
4. rpcbind is not part of ti-rpc library. I was confused by man file
with this name.
I read about this problem, but i don't really understand this
SO_REUSEADDR trick. So i decided not to modify the tirpc code, assuming
it works, and it's some WinSock-specific glitch. Instead i quickly
ported rpcbind (http://sourceforge.net/projects/rpcbind/), and the whole
thing runs correctly now.
--
Kind regards
Pavel Fedin
Expert engineer, Samsung Moscow research center
--
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
prev parent reply other threads:[~2012-05-14 7:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 5:42 Fedin Pavel
2012-05-14 7:52 ` Fedin Pavel [this message]
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=4FB0B9B0.10503@samsung.com \
--to=p.fedin@samsung.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).