DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=WoQoPJAMzhWPR23oFOioSN/U3HWPW730ObSpDQy2eHRGWaqTxRaDI
	rECGIE+ymq6NtVuHXPbv2nXffz/Imrf5CpG03BYni5zPudxEudI0HJHLQbVFAyx3
	fM+WsazR2ng1sI1qDe9InL/qTTOCH25U79Iuh8SeHY7gEiKF0WKRAY=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Tue, 14 Oct 2014 21:50:43 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: lwp-request stopped working with snapshots
Message-ID: <20141014195043.GH2681@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <877g025x6i.fsf@Rainer.invalid> <20141014193408.GG2681@calimero.vinschen.de> <87y4si4ewp.fsf@Rainer.invalid>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="4nkDkwsKLd7vqNiU"
Content-Disposition: inline
In-Reply-To: <87y4si4ewp.fsf@Rainer.invalid>
User-Agent: Mutt/1.5.23 (2014-03-12)

--4nkDkwsKLd7vqNiU
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Oct 14 21:41, Achim Gratz wrote:
> Corinna Vinschen writes:
> > lwp-request is one of the tools using connect to try if a former
> > non-blocking connect worked.  This is ugly but, sigh, valid behaviour,
>=20
> What should it be doing instead?  LWP upstream has switched to a new
> maintainer recently IIRC, so it might be a good time to suggest a few
> cleanups.

Calling select or poll instead.  But, anyway, uglyness is in the eye of
the beholder and ultimately it *is* a valid approach and it worked
before.  So it was clearly a newly introduced bug in Cygwin.

> > The latest changes to the socket code didn't take this scenario into
> > account.  I applied a fix and uploaded a new snashot to
> > https://cygwin.com/snapshots/
> >
> > Please give it a try.
>=20
> I sure will do this first thing tomorrow, thanks!

Oh, good!  I just realized that I missed to handle EALREADY, so I
applied YA patch and just replaced the snapshot with a new one.


Thanks,
Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--4nkDkwsKLd7vqNiU
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJUPX6TAAoJEPU2Bp2uRE+gjX8P/1Qbg7JeWAiTL/wBR2ynL7iu
gmVqgPn9gd3gdSmMVCAyUVvM1y20rAJUfq2beS3ArALyCfbqy4QQJfWigcNcJiLc
Jx4SCQbkLwvMnOxZxKjAhliqK5I7TMj6l8JU0AgdHfpK7D4upARUsrYXMHtpBMVO
TZRqWVHAijQCGj6O8gPZrSzxlvfGEiYgxfySN4dPV0EIm/unuPFDd2ASecBsOOmh
JkXCqv+Qd92gW7O2jvHw+qUEv/v1gwxeA8NP+oNAxNoq/Hx6yoVIxW84rr01RztA
AexPuaqgc2iBo9ardEzr7yN2iaR0AgnMl5me/5ZVWX/XIXSKcgifRL4SrpZHC5bc
na1WYU7N41c59ZmxrB/ie3lyeSeHBWE36zhZVf/m/LQEwK5y8+mJk3j65wkW8+qI
c+fTtAKd7iYG690TutmxxbsttYahwQig2pQtTcSBoMyOUqeSA3MszteHTt6Pirr3
dcZftltbE05UBnRoRGmCJDaA1ieilOXFZRwY9WPZBxPJqg+Q1E/7dg+8twt62n+6
6Bjgpo6i60Y98rBzlUpvk/u2iP3MLmn/KARyDjm8ytdkk/8Rj3iP28QjQB6jonS0
Uh247aPLnyiIR0sA7SabLNSMPkAWqc0bvJL5uDVZ8jYolmwE/+XiqOfK8UDlCTsl
fDcuY90vrzGK1WgsX0OS
=DmGe
-----END PGP SIGNATURE-----

--4nkDkwsKLd7vqNiU--