From: Bernd Eckenfels <ecki-news2002-02@lina.inka.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH-RFC] POSIX Event Logging, kernel 2.5.6 & 2.4.18
Date: Wed, 13 Mar 2002 02:10:50 +0100 [thread overview]
Message-ID: <E16kxI2-0003aI-00@sites.inka.de> (raw)
In-Reply-To: <3C8E8912.64435C1E@us.ibm.com>
In article <3C8E8912.64435C1E@us.ibm.com> you wrote:
> I assume that you mean do the nasty stuff but never have anything in
> your
> event log indicating that it happened. Good point, but if the buffer is
> sized appropriately for the incoming volume of events and the logging
> daemon
> is reading the events out of the kernel buffer (as should normally be
> the case),
> then you would see the events.
Well, depending on the type of events one can even think about a "halt" like
it is required for audit trail overflow.
What would be nice is a policy for each type of event:
- overwrite old/new/halt
- rate limit
- buffer size
next prev parent reply other threads:[~2002-03-13 1:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-12 22:15 Larry Kessler
2002-03-12 22:41 ` Dominik Kubla
2002-03-12 23:02 ` Larry Kessler
2002-03-13 1:10 ` Bernd Eckenfels [this message]
2002-03-13 0:33 ` Bernd Eckenfels
2002-03-14 1:07 Larry Kessler
2002-03-14 2:32 ` Bernd Eckenfels
2002-03-14 19:45 ` Brian Beattie
2002-03-15 1:10 ` Larry Kessler
2002-03-15 1:17 Larry Kessler
2002-03-15 17:57 Larry Kessler
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=E16kxI2-0003aI-00@sites.inka.de \
--to=ecki-news2002-02@lina.inka.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®