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 X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Tue, 3 Feb 2004 10:54:40 -0500 (EST) From: Igor Pechtchanski Reply-To: cygwin@cygwin.com To: =?iso-8859-1?Q?Lutz_H=F6rl?= cc: cygwin@cygwin.com Subject: Re: Is there a translation from windows events to cygwin signals ? In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT On Tue, 3 Feb 2004, Lutz Hörl wrote: > Hello, > > My problem: > > I have to send a signal to a running cygwin application, but I can not > use the cygwin API for this purpose. This doesn't make sense. You can always do system("c:/cygwin/bin/kill -HUP "). > This signal (e.g. SIGHUP) can be cought by my cywin application, the > application can react on it in a proper way. > > Until now I found only documentation that states that the cygwin signals > rely on windows events but no documentation on how to use this > mechanism. > > Is there a 'translation' from windows events into signals ? > Is there a way to use then Win32 "BroadcastSystemMessage()" function to > send a Signal to cygwin application ? > > Thank you all > Lutz Hoerl Cygwin signals use Windows events under the covers, but there's more to Cygwin signals than just Windows events. There's no one-to-one mapping. Use "kill". Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha@cs.nyu.edu ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "I have since come to realize that being between your mentor and his route to the bathroom is a major career booster." -- Patrick Naughton -- 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/