From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 116073 invoked by alias); 30 Jan 2018 07:01:47 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 116051 invoked by uid 89); 30 Jan 2018 07:01:45 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.6 required=5.0 tests=AWL,BAYES_50,CYGWIN_OWNER_BODY,GIT_PATCH_2,KAM_INFOUSMEBIZ,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 spammy=premium, Premium, Laptop, ursprngliche X-HELO: mailrelay.dillinger.de Received: from mailrelayb.dillinger.de (HELO mailrelay.dillinger.de) (212.184.64.29) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 30 Jan 2018 07:01:40 +0000 Received: from mailrelaya2.dillinger.de (mailrelaya [192.168.175.11]) by lin254mailrelayb.dillinger.de (Postfix) with ESMTP id 7DE85A34B for ; Tue, 30 Jan 2018 08:01:37 +0100 (CET) Received: from lin275.int.shsservices.de (lin275 [172.18.32.6]) by mailrelaya2.dillinger.de (Postfix) with ESMTP id D15FD2422FE for ; Tue, 30 Jan 2018 08:11:02 +0100 (CET) Received: from RESW103.resdom01.local (resw103.dillinger.de [172.18.22.103]) by lin275.int.shsservices.de (Postfix) with ESMTP id 6410FF3EFB for ; Tue, 30 Jan 2018 08:01:37 +0100 (CET) Received: from RESW102.resdom01.local ([fe80::a883:3db9:4459:1159]) by RESW103.resdom01.local ([fe80::a480:c1ef:e5bb:a91b%15]) with mapi id 14.03.0279.002; Tue, 30 Jan 2018 08:01:37 +0100 From: "PAULUS, Raimund, TI-ABN" To: "cygwin@cygwin.com" Subject: Re: RPC clnt_create() adress already in use Date: Tue, 30 Jan 2018 07:01:00 -0000 Message-ID: <59D90AF8D70E9740907BACDE2BCB520836DFC167@RESW102.resdom01.local> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-IsSubscribed: yes X-SW-Source: 2018-01/txt/msg00286.txt.bz2 Hi Mark, as Corinna wrote in the thread " Cygwin socket option SO_REUSEADDR operates= unlike Linux", the cause for the problem in libtirpc is Microsofts impleme= ntation of socket handling. If i implement a simple socket client, that is = not so much of an issue, because I call the functions separately and can ha= ndle the error. Moreover in this case bind() is not necessary. But in the case of libtirpc the implementation of clnttcp_create() determin= es the sequence of bind() and connect() for the local port and you cannot c= orrect the error of bind() after the call of connect(). Therefore I think b= est is to set the port number to zero (port =3D 0) before the call to bind(= ). Raimund -----Urspr=FCngliche Nachricht----- Von: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] Im Auftrag vo= n PAULUS, Raimund, TI-ABN Gesendet: Dienstag, 9. Januar 2018 09:14 An: cygwin@cygwin.com Betreff: WG: AW: RPC clnt_create() adress already in use Hi Mark, i have just tested it with the client-program from my email from December 2= 9. The server-program is running on a linux-machine (SuSE Enterprise). I compiled and linked the client.exe in Cygwin 1.5.18 on a PC with Windows = XP SP3 and it works (loop 100 times). It was running in the bash-shell. Thereafter I copied the client.exe to a Laptop with Windows 7 Home Premium.= I started the program from the command prompt (cmd.exe) because rxvt doesn= 't work.=20 The program works (loop 100 times). Greetings Raimund -----Urspr=FCngliche Nachricht----- Von: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] Im Auftrag vo= n Mark Geisert Gesendet: Dienstag, 9. Januar 2018 05:52 An: cygwin@cygwin.com Betreff: Re: AW: RPC clnt_create() adress already in use 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 ver= sions. 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 ha= s 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 -- 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 -- 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