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
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Sat, 19 Jan 2002 19:04:03 -0500
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: problem with sigaction and SA_NOCLDSTOP
Message-ID:	<20020120000403.GA6765@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<002601c1a133$921c0b40$0100a8c0 AT advent02>
Mime-Version:	1.0
In-Reply-To:	<002601c1a133$921c0b40$0100a8c0@advent02>
User-Agent:	Mutt/1.3.23.1i

On Sat, Jan 19, 2002 at 09:52:19PM -0000, Chris January wrote:
>sigaction has a flag, SA_NOCLDSTOP, which according to the POSIX spec does
>this:
>
>SA_NOCLDSTOP
>Do not generate SIGCHLD when children stop.
>
>Now Cygwin presently does not generate a SIGCHLD signal when a child process
>terminates if this flag is set in the signal handler.

I've just checked in a fix for this.  It should be in the next cygwin snapshot.

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 -