Re: connect() not interrupted by sigalrm?

Dear Corinna, 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 portabilit

Re: connect() not interrupted by sigalrm?

Dear Corinna, > 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.

Re: connect() not interrupted by sigalrm?

Thanks, Elfyn, > I believe I have found the problem. In order for your program to work as > expected you will need SA_INTERRUPT , which is not defined in > /usr/include/sys/signal.h . So it just laggs until it gets to the "Network > unreachable" error. I'm not to sure the reason why it's not ther

Re: connect() not interrupted by sigalrm?

Dear Elfyn, Thanks for your prompt response: > Cockpit error. You left out a few headers. > - string.h is needed for memset() > - unistd.h is needed for alarm() > - arpa/inet.h is needed for inet_addr() > > After that it works fine. The addition of these include files does make gcc -Wall happi

connect() not interrupted by sigalrm?

seems as if CancelIo() doesn't work with WSARecv() on 98/Me. I've search for info in MSDN and I've asked in newsgroups but to no avail so far... Is the answer the same for connect()? Regards, Eric Mandel /* * solaris: gcc -o atest atest.c -lsocket -lnsl * linux: gcc -o at