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 Date: Fri, 28 Jun 2002 10:53:13 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: 1.3.11: accept ist not interrupted by a signal Message-ID: <20020628145313.GC4490@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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/