Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Subject:	1.3.11: accept ist not interrupted by a signal
MIME-Version:	1.0
Date:	Fri, 25 Oct 2002 15:17:56 +0200
X-MimeOLE:	Produced By Microsoft Exchange V6.0.6249.0
Message-ID:	<2DFB37B7D3EBFD4BB4FEDEC443C50B330C16D5@mailserver>
content-class:	urn:content-classes:message
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
From:	"Franck Leray" <franck DOT leray AT cheops DOT fr>
To:	<cygwin AT cygwin DOT com>
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id g9PDF6Q30724

Hi all,

A process waiting for clients on a 'accept' statement becomes mad (eating cpu) when it receives a signal.
Not on UNIX platform.

See the message of Christopher Faylor (28 jun 2002) '1.3.11: accept ist not interrupted by a signal' for an example.

I don't want to use a non-blocking socket.

Is there an other solution ?
Is it a bug ?

Franck.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -