X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-7.1 required=5.0	tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=windows-1251; format=flowed
Date: Mon, 14 May 2012 11:52:16 +0400
From: Fedin Pavel <p DOT fedin AT samsung DOT com>
Subject: Re: RPC inconsistency
In-reply-to: <4FB09B1A.70004@samsung.com>
To: cygwin AT cygwin DOT com
Message-id: <4FB0B9B0.10503@samsung.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:10.0) Gecko/20120206 Thunderbird/10.0
References: <4FB09B1A DOT 70004 AT samsung DOT com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT 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