This is the mail archive of the
mailing list for the Cygwin project.
Re: connect() not interrupted by sigalrm?
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 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