Mail Archives: cygwin-developers/2002/07/04/07:56:28

Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
X-Authentication-Warning: mail set sender to <tpfaff AT gmx DOT net> using -f
Date: Thu, 4 Jul 2002 13:54:33 +0200 (=?ISO-8859-1?Q?Westeurop=E4ische_Sommerzeit?=)
From: Thomas Pfaff <tpfaff AT gmx DOT net>
To: cygwin-developers AT cygwin DOT com
Subject: Interruptable connect
Message-ID: <>
X-X-Sender: pfaff AT antarctica DOT intern DOT net
MIME-Version: 1.0

I am trying to get an interruptable connect and i have some difficulties.

The main problem is that it seems to be impossible to cancel a nonblocking
connect other than closing the socket. I already thought about closing the
socket and replacing it with a new one, but this requires that all
sockoptions and states have to be restored for the new one execpt the
pending connect.

Another possibility is to set errno to EINTR, return and let the
connect keep going.
The app can now react in different ways :

The signal handler terminates the program.

The program checks for the error and close the socket.

connect is called in a loop like
do {
  res = connect(...);
  if (!res)
} while(errno==EINTR);
Now the program returns to the connect function, the real connect returns
WSAEALREADY or WSAEISCONN, it can be checked that the connect was
interrupted and it can be continued.
No big deal.

The error is ignored and the socket is not closed:
Now there are 2 possibilies.

a. The connect fails.
No problem.

b. The connect succeds. Now exists an orphaned connection that can block
the partner.

Any suggestions ?


- Raw text -

  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019