Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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, 6 Feb 2004 11:28:14 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Signal handling failed when using msgrcv - CYGWIN 1.5.7 Message-ID: <20040206102814.GO26148@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Feb 6 00:57, Luc DOT VanKeer AT ordina-denkart DOT com wrote: > I have a process that waits on a message queue (with msgrcv) and has > installed a signal handler. > When another process send a signal (e.g. SIGTERM) to this process, the > signal handler is not called. > This was working in version 1.5.5 using the ipc2-deamon, but stopped > working after switching to version 1.5.7 and using cygserver for the > message queue implementation. Thanks for the report. Actually that's a problem in the current implementation of Cygserver. I'm looking into it. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/