From: Klaus Heinrich Kiwi <klausk@br.ibm.com>
To: linux-audit@redhat.com
Subject: Re: event loss with dispatcher?
Date: Mon, 7 Jan 2008 13:21:30 +0000 (UTC) [thread overview]
Message-ID: <flt90q$o49$1@ger.gmane.org> (raw)
In-Reply-To: 1194540856.19673.26.camel@klausk.br.ibm.com
On Thu, 08 Nov 2007 11:54:16 -0500, Klaus Heinrich Kiwi wrote:
> Hi,
>
> I'm trying to debug a potential problem with the dispatcher mechanism
> in version 1.6.2. Long story short, I saw that some records were being
> missed in the remote system (using the audisp-racf plugin), couldn't
> find anything wrong with the code, so I enabled the syslog plugin,
> trying to match the the syslog with the audit log output - At least in
> my system, they are not matching.
...
Looks like this was fixed in 1.6.4
-Klaus K.
next prev parent reply other threads:[~2008-01-07 13:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 16:54 event loss with dispatcher? Klaus Heinrich Kiwi
2007-11-08 17:34 ` Steve Grubb
2007-11-08 21:17 ` klausk
2007-11-08 21:55 ` Steve Grubb
2007-11-09 2:20 ` John Dennis
2007-11-09 14:23 ` Steve Grubb
2008-01-07 13:21 ` Klaus Heinrich Kiwi [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-08 23:15 Klaus Heinrich Kiwi
2007-11-09 4:09 ` James Antill
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='flt90q$o49$1@ger.gmane.org' \
--to=klausk@br.ibm.com \
--cc=linux-audit@redhat.com \
/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