X-Spam-Check-By: sourceware.org Date: Mon, 28 Nov 2005 13:22:22 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Query: issue with cygwin-curl 7.15.0 - cannot close some connections Message-ID: <20051128122222.GI2999@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <3ace93110511280052i67bd114cn6664a26864a24eaa AT mail DOT gmail DOT com> <438AF263 DOT DC178000 AT dessent DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <438AF263.DC178000@dessent.net> User-Agent: Mutt/1.4.2i Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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 Nov 28 04:04, Brian Dessent wrote: > The reason that it apparently did not realize that the connection had > been terminated was that the Cygwin poll() was returning 1 with the > POLLHUP bit set in 'revents'. But curl was not aware of this bit and > only looked for POLLIN, so it got confused, which caused the infinite > loop. > > This was changed several weeks ago in Cygwin by this: > which means that > if you use a recent snapshot (and presumably the forthcoming 1.5.19 > release) you should not experience the problem. > > I'm debating whether it would be a good idea to put out an updated curl > that checks for POLLHUP to get things working again with older cygwins. Sounds like a good idea. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/