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
Date:	Fri, 28 Jun 2002 10:53:13 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: 1.3.11: accept ist not interrupted by a signal
Message-ID:	<20020628145313.GC4490@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<Pine DOT WNT DOT 4 DOT 44 DOT 0206281405210 DOT 269-100000 AT algeria DOT intern DOT net>
Mime-Version:	1.0
In-Reply-To:	<Pine.WNT.4.44.0206281405210.269-100000@algeria.intern.net>
User-Agent:	Mutt/1.3.23.1i

On Fri, Jun 28, 2002 at 02:34:16PM +0200, Thomas Pfaff wrote:
>
>I am a bit confused about the current signal handling in a blocking
>accept call (i have not checked other system calls yet)
>If the process is blocked it is not interrupted by a signal.

Yep, unfortunately that's how it works currently.

cgf

--
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 -