From: "Berger, Daniel" Date: 2005-09-21T23:38:32+09:00 Subject: Re: signals and win32 > -----Original Message----- > From: Ara.T.Howard [mailto:Ara.T.Howard@noaa.gov] > Sent: Tuesday, September 20, 2005 8:39 PM > To: ruby-talk ML > Subject: signals and win32 > > > > can someone show me a working example of trapping a signal > sent to a process using the extended Process::kill enabled by > win32-process? i can't seem to figure this out - all signals > sent seem to behave like signal 9: the process simply aborts. The only "signals" that Process.kill supports in win32-process are "Ctrl-C" and "Ctrl-Break", signals 2 and 3 respectively. Signal 0 does not kill a process. It merely tells you if it's running or not. Signals 1, and 4-8 kill the process using CreateRemoteThread(). Signal 9 kills the process via TerminateProcess(). Can you provide a code sample that isn't working properly? And what version of win32-process and what platform you're running on? Regards, Dan