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 10:16:23 -0500
- Subject: Re: connect() not interrupted by sigalrm?
- References: <200302241757.h1OHvQN16044@head-cfa.cfa.harvard.edu>
> The Cygwin connect() call isn't interruptible so far.
> It's possible to change it to an interruptible call but that
> requires some coding.
> In the meantime, how about using a non-blocking connect() and a call to
> select() instead?
Thanks for your prompt reply and suggestion. Consideration of a (more
complicated) non-blocking connect() scheme depends on whether you
think an interruptible connect() call might actually be coded at some
point. If its the sort of thing that would be a good idea in an ideal
world, but which probably will not get done under current circumstances
(i.e., too hard for the small return), then the complications of
non-blocking connect would have to be considered. Otherwise, I prefer
to wait in hope.
Your clarification on this point would be appreciated -- even if its
"I don't know".
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html