From: mail@justinbogner.com
To: emacs-devel@gnu.org
Subject: Re: Functions in kill-emacs-hook aren't run if emacs gets killed with SIGTERM
Date: Thu, 22 Jan 2009 19:15:30 -0700 [thread overview]
Message-ID: <87mydircn0.fsf@justinbogner.com> (raw)
In-Reply-To: uhc3rurm0.fsf@gnu.org
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Tassilo Horn <tassilo@member.fsf.org>
>> Is SIGTERM really such a fatal signal as you say? I always believed
>> SIGTERM meant "shutdown, but do it cleanly" whereas SIGKILL meant "Die!
>> Die! Die! NOW!".
>
> No, the reason is that SIGKILL cannot be caught or ignored, whereas
> SIGTERM can. Which has the practical effect that you mention, but
> it's IMO important to understand the underlying reason.
I don't understand what you're trying to say. The reason that SIGKILL
cannot be ignored is that it means "Die! Die! Die! NOW!", and the reason
that SIGTERM can is that it means "shutdown, but do it cleanly". Ie, the
reasons and practical effects are exactly opposite of what you seem to
be saying: could you explain in more detail?
next prev parent reply other threads:[~2009-01-23 2:15 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 8:06 Functions in kill-emacs-hook aren't run if emacs gets killed with SIGTERM Tassilo Horn
2009-01-21 18:42 ` Eli Zaretskii
2009-01-21 19:49 ` Tassilo Horn
2009-01-21 20:35 ` Chong Yidong
2009-01-22 9:03 ` Tassilo Horn
2009-01-21 20:36 ` Stefan Monnier
2009-01-22 4:09 ` Eli Zaretskii
2009-01-22 9:00 ` Tassilo Horn
2009-01-22 18:23 ` Eli Zaretskii
2009-01-23 2:15 ` mail [this message]
2009-01-23 12:05 ` Eli Zaretskii
2009-01-22 10:08 ` Andreas Schwab
2009-01-22 18:25 ` Eli Zaretskii
2009-01-23 1:52 ` Richard M Stallman
2009-01-22 14:41 ` Stefan Monnier
2009-01-22 18:32 ` Eli Zaretskii
2009-01-22 21:16 ` Stefan Monnier
2009-01-23 15:25 ` Eli Zaretskii
2009-01-23 15:58 ` Tassilo Horn
2009-01-23 19:06 ` Eli Zaretskii
2009-01-23 19:56 ` David De La Harpe Golden
2009-01-23 22:39 ` Eli Zaretskii
2009-01-23 23:00 ` Tassilo Horn
2009-01-23 23:13 ` Lennart Borgman
2009-01-24 9:04 ` Tassilo Horn
2009-01-24 9:59 ` Eli Zaretskii
2009-01-24 12:34 ` Miles Bader
2009-01-24 10:00 ` Eli Zaretskii
2009-01-23 20:33 ` Dan Nicolaescu
2009-01-23 22:37 ` Eli Zaretskii
2009-01-24 4:40 ` Jason Rumney
2009-01-24 6:11 ` Miles Bader
2009-01-23 1:52 ` Richard M Stallman
-- strict thread matches above, loose matches on Subject: below --
2009-01-23 19:01 grischka
2009-01-23 22:52 ` Eli Zaretskii
2009-01-24 14:16 ` grischka
2009-01-24 16:14 ` Eli Zaretskii
2009-01-24 17:56 ` grischka
2009-01-24 18:20 ` Eli Zaretskii
2009-01-24 19:11 ` grischka
2009-01-24 20:08 ` Eli Zaretskii
2009-01-24 20:28 ` grischka
2009-01-24 20:32 Stefan Monnier
2009-02-02 20:23 ` Eli Zaretskii
2009-02-02 20:52 ` Tassilo Horn
2009-02-02 21:09 ` Eli Zaretskii
2009-02-03 10:43 ` Tassilo Horn
2009-02-05 3:34 ` Stefan Monnier
2009-01-24 20:39 Stefan Monnier
2009-02-03 17:28 grischka
2009-02-05 3:37 ` Stefan Monnier
2009-02-05 13:31 ` grischka
2009-02-05 19:40 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mydircn0.fsf@justinbogner.com \
--to=mail@justinbogner.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).