Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Tue, 25 Feb 2003 17:04:32 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: connect() not interrupted by sigalrm? Message-ID: <20030225160432.GO8853@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <200302241757.h1OHvQN16044@head-cfa.cfa.harvard.edu> <200302251516.h1PFGNN22512@head-cfa.cfa.harvard.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200302251516.h1PFGNN22512@head-cfa.cfa.harvard.edu> User-Agent: Mutt/1.4i On Tue, Feb 25, 2003 at 10:16:23AM -0500, Eric Mandel wrote: > Your clarification on this point would be appreciated -- even if its > "I don't know". We're discussing that matter but it's not expected to be a quick or full solution. There are problems with the way WinSock works. So the answer is "I don't know". Btw., switching to non-blocking for the connect/select pair isn't actually difficult so I wonder what your problem is. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/