This is the mail archive of the cygwin@sourceware.cygnus.com
mailing list for the Cygwin project. See the Cygwin
home page for more information.
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index] [Subject Index] [Author Index] [Thread Index]
Re: Signal Handling on W95
- To: Jason Moxham <jlm@maths.soton.ac.uk>
- Subject: Re: Signal Handling on W95
- From: Anders Norlander <anorland@hem2.passagen.se>
- Date: Fri, 19 Mar 1999 18:51:20 +0100
- CC: cygwin@sourceware.cygnus.com
- Delivered-To: listarch-cygwin@sourceware.cygnus.com
- Delivered-To: mailing list cygwin@sourceware.cygnus.com
- Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
- References: <199903191650.QAA01744@mir.maths.soton.ac.uk>
- Sender: cygwin-owner@sourceware.cygnus.com
Jason Moxham wrote:
>
> I have a program which traps signals so that upon receiving a SIGTERM it
> can exit properly by saving data files etc ,
>
> When shutdown is activated on Windows 95 , no SIGTERM signals are sent
> so data files etc may be left in an inconsistent state
>
> Q) What signal is sent on shutdown ? , if SIGKILL can we trap it?
>
> Q) If no signal is sent , what conditions can we test to allow for a
> clean exit
This is a windows 95 feature and it is mentioned in the win32 docs.
Simply doesn't work.
On NT I think cygwin sends a SIGHUP signal, although I'm not sure if it
works.
Regards,
Anders
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com