Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Subject: 1.3.11: accept ist not interrupted by a signal MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" 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" To: Content-Transfer-Encoding: 8bit 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/