From: Michael Schmarck <michael.schmarck@habmalnefrage.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Re: Re: Emergency shutdown, how to?
Date: Thu, 03 Apr 2008 10:56:28 +0200 [thread overview]
Message-ID: <1441927.enUePkHcfs@schmarck.cn> (raw)
In-Reply-To: 20080403094113.64eaa6c5@loonquawl.digimed.co.uk
Neil Bothwick <neil@digimed.co.uk> wrote:
> On Thu, 03 Apr 2008 06:51:28 +0200, Michael Schmarck wrote:
>
>> But nonetheless, there's still the risk that the KILL has
>> destroyed the application database (sort of - more correctly:
>> that the application and its database was in a "non consistent"
>> state when it received the signal).
>
> Yes, but in that case the application has already failed, otherwise it
> would have shut down on TERM.
Maybe it would have recoverd in "due time". The chances are pretty
slim, but they are >0.
> Emergency shutdowns aren't about
> eliminating any problems in the case of a serious system hang, they are
> about minimising such damage.
Absolutely correct! But Liviu asked, if there's a potential risk
to the system.
My answer is: Yes, there is! It is pretty low (for the reasons
you mentioned), but it is not 0.
Michael
--
gentoo-user@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-04-03 8:56 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 7:33 [gentoo-user] Emergency shutdown, how to? Dale
2008-03-28 7:41 ` Daniel Pielmeier
2008-03-28 7:46 ` Dirk Heinrichs
2008-03-28 7:51 ` Daniel Pielmeier
2008-03-28 8:07 ` Dale
2008-03-28 8:11 ` Dirk Heinrichs
2008-03-28 10:12 ` Michal 'vorner' Vaner
2008-04-02 13:36 ` Liviu Andronic
2008-04-02 13:44 ` [gentoo-user] " Michael Schmarck
2008-04-02 13:49 ` Dirk Heinrichs
2008-04-02 14:19 ` [gentoo-user] " Michael Schmarck
2008-04-02 14:28 ` [gentoo-user] " Dirk Heinrichs
2008-04-02 14:41 ` Mark Knecht
2008-04-02 15:18 ` Neil Bothwick
2008-04-02 20:58 ` darren kirby
2008-04-02 22:24 ` Neil Bothwick
2008-04-02 17:40 ` [gentoo-user] " Michael Schmarck
2008-04-02 17:48 ` Neil Bothwick
2008-04-03 4:51 ` [gentoo-user] " Michael Schmarck
2008-04-03 8:41 ` Neil Bothwick
2008-04-03 8:56 ` Michael Schmarck [this message]
2008-04-04 0:28 ` [gentoo-user] " Iain Buchanan
2008-04-04 21:05 ` [gentoo-user] " Mark Knecht
2008-04-04 21:50 ` Neil Bothwick
2008-04-04 22:14 ` Mark Knecht
2008-04-05 16:42 ` Steven Lembark
2008-04-07 1:07 ` Iain Buchanan
2008-04-07 17:28 ` Steven Lembark
2008-04-07 23:29 ` Iain Buchanan
2008-04-08 18:19 ` Steven Lembark
2008-04-02 15:50 ` [gentoo-user] " Steven Lembark
2008-04-02 17:28 ` Volker Armin Hemmann
2008-04-02 19:19 ` Dale
2008-04-02 19:57 ` Mark Knecht
2008-04-02 21:42 ` Neil Bothwick
2008-04-02 19:59 ` Volker Armin Hemmann
2008-04-02 21:43 ` Neil Bothwick
2008-04-02 21:56 ` Dale
2008-04-03 2:35 ` Hal Martin
2008-04-03 16:10 ` Steven Lembark
2008-04-03 18:15 ` Dale
2008-04-03 19:38 ` Steven Lembark
2008-04-04 0:45 ` Dale
2008-04-04 17:04 ` Steven Lembark
2008-04-04 19:52 ` Dale
2008-04-04 20:24 ` Steven Lembark
2008-04-04 0:29 ` Iain Buchanan
2008-04-04 1:00 ` Dale
2008-04-04 17:06 ` Steven Lembark
2008-04-07 6:42 ` Dan Farrell
2008-04-07 20:14 ` Steven Lembark
2008-03-28 8:29 ` Neil Bothwick
2008-03-28 11:09 ` Dale
2008-03-28 7:42 ` Dirk Heinrichs
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1441927.enUePkHcfs@schmarck.cn \
--to=michael.schmarck@habmalnefrage.de \
--cc=gentoo-user@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox