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: > <http://cygwin.com/ml/cygwin-cvs/2005-q4/msg00077.html> 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/
