Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Tue, 25 Feb 2003 18:46:42 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: connect() not interrupted by sigalrm? Message-ID: <20030225174642.GS8853@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <200302241757 DOT h1OHvQN16044 AT head-cfa DOT cfa DOT harvard DOT edu> <200302251718 DOT h1PHI4N00913 AT head-cfa DOT cfa DOT harvard DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200302251718.h1PHI4N00913@head-cfa.cfa.harvard.edu> User-Agent: Mutt/1.4i On Tue, Feb 25, 2003 at 12:18:04PM -0500, Eric Mandel wrote: > Cf. Stevens "Unix Network Programming", section 15.3: > > "There are many portability problems with nonblocking connnects > that we mention in the examples that follow." > > and, after a lengthy discussion of portability issues: > > "Unfortunately, nonblocking connects are one of the most nonportable > areas of network programming." Cygwin is trying to be POSIX conformant in the first place and Linux in the second. However, thanks for the pointer to Stevens. I have this book as well but I didn't read the connect stuff intently. There's an interesting sub chapter "Interrupted connect" which could help implementing... well... interrupted connects. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT 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/