From: Folkert van Heusden <folkert@vanheusden.com>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] emit logging when a process receives a fatal signal
Date: Sat, 18 Nov 2006 14:32:05 +0100 [thread overview]
Message-ID: <20061118133205.GE31268@vanheusden.com> (raw)
In-Reply-To: <200611181146.kAIBkW52028010@harpo.it.uu.se>
> 4. If this is about detecting the loss of specific processes
> (network services say), then the problem can be solved in
> user-space by using a separate monitor process, or by
> controlling the processes via ptrace.
No not only for specific processes. It helps you detect problems with
processes you dind't know they have bugs and flakey hardware (sig 11).
Folkert van Heusden
--
Ever wonder what is out there? Any alien races? Then please support
the seti@home project: setiathome.ssl.berkeley.edu
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com
next prev parent reply other threads:[~2006-11-18 13:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-18 11:46 [PATCH] emit logging when a process receives a fatal signal Mikael Pettersson
2006-11-18 13:32 ` Folkert van Heusden [this message]
2006-11-18 19:31 ` Jan Engelhardt
-- strict thread matches above, loose matches on Subject: below --
2006-11-18 1:09 Folkert van Heusden
2006-11-18 1:26 ` Oleg Verych
2006-11-18 2:02 ` Folkert van Heusden
2006-11-18 2:04 ` Folkert van Heusden
2006-11-18 2:38 ` Oleg Verych
2006-11-18 10:39 ` Miquel van Smoorenburg
2006-11-18 14:09 ` Oleg Verych
2006-11-18 19:30 ` Jan Engelhardt
2006-11-18 21:51 ` Oleg Verych
2006-11-18 23:24 ` Jan Engelhardt
2006-11-19 7:13 ` Oleg Verych
2006-11-19 10:47 ` Jan Engelhardt
2006-11-21 3:48 ` Marty Leisner
2006-11-21 5:47 ` Oleg Verych
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=20061118133205.GE31268@vanheusden.com \
--to=folkert@vanheusden.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
/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