This is the mail archive of the
mailing list for the Cygwin project.
Re: connect() not interrupted by sigalrm?
- From: Eric Mandel <eric at head-cfa dot harvard dot edu>
- To: cygwin at cygwin dot com
- Cc: eric at head-cfa dot cfa dot harvard dot edu
- Date: Tue, 25 Feb 2003 12:18:04 -0500
- Subject: Re: connect() not interrupted by sigalrm?
- References: <200302241757.h1OHvQN16044@head-cfa.cfa.harvard.edu>
Thanks for the quick clarification on plans for interruptible connect().
> Btw., switching to non-blocking for the connect/select pair isn't
> actually difficult so I wonder what your problem is.
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."
Since my code must run on several flavors of Unix, I hesitate to use
this technique. I suppose I could use it solely for Cygwin and retain
the more portable alarm()/connect() technique for the other platforms,
and that is what I am considering now.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html