From: Folkert van Heusden <folkert@vanheusden.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, alexander.riesen@synopsys.COM
Cc: bert hubert <ahu@ds9a.nl>, Mo McKinlay <lkml@ekto.ekol.co.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: logging when SIGSEGV is processed?
Date: Mon, 15 Sep 2003 18:05:51 +0200 [thread overview]
Message-ID: <200309151805.52153.folkert@vanheusden.com> (raw)
In-Reply-To: <1063612045.3734.6.camel@dhcp23.swansea.linux.org.uk>
> On Llu, 2003-09-15 at 08:09, Alex Riesen wrote:
> > Probably ptrace the daemon (following all its children) would server
> > better. The feature (logging the coredumps) is definitely no needed for
> > everything, just some suspectables.
> accton() will turn on logging and that gives you log records of process
> termination including if it segfaulted.
Sound's good. You probably mean acct()? There's one little problem with that
one:
NOTES
No accounting is produced for programs running when a
crash occurs. In particular, nonterminating processes are
never accounted for.
Folkert van Heusden
+--------------------------------------------------------------------------+
| UNIX sysop? Then give MultiTail ( http://www.vanheusden.com/multitail/ ) |
| a try, it brings monitoring logfiles (and such) to a different level! |
+---------------------------------------------------= www.vanheusden.com =-+
next prev parent reply other threads:[~2003-09-15 16:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-14 11:14 Mo McKinlay
2003-09-14 17:17 ` bert hubert
2003-09-15 7:09 ` Alex Riesen
2003-09-15 7:47 ` Alan Cox
2003-09-15 16:05 ` Folkert van Heusden [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-14 1:28 Folkert van Heusden
2003-09-14 2:18 ` Joshua Kwan
2003-09-14 7:23 ` Folkert van Heusden
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=200309151805.52153.folkert@vanheusden.com \
--to=folkert@vanheusden.com \
--cc=ahu@ds9a.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alexander.riesen@synopsys.COM \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@ekto.ekol.co.uk \
/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
all inboxes | Powered by JetHome®