public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: John Dennis <jdennis@redhat.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: "Linux-audit@redhat.com" <Linux-audit@redhat.com>
Subject: Re: event loss with dispatcher?
Date: Thu, 08 Nov 2007 21:20:42 -0500	[thread overview]
Message-ID: <4733C3FA.9000005@redhat.com> (raw)
In-Reply-To: <200711081655.23068.sgrubb@redhat.com>

Steve Grubb wrote:
> On Thursday 08 November 2007 16:17:52 klausk@br.ibm.com wrote:
>> Any tips on how can I debug this further?

My apologies, but I haven't been following this thread because I've had 
my head down with other work, but by any chance could the missing audit 
data be explained by out of order event ID's in the audit stream? This 
was a limitation of auparse but I know Steve was planning on fixing 
this. If it hasn't been fixed auparse will appear to drop audit records 
from an event if the audit records for a single event are not 
contigious. Actually I think you'll get multiple copies of the same 
event with each copy containing only part of the audit data, a scenario 
that's confusing and would give the appearance of missing data. Just a 
thought, not sure if it's relevant.

-- 
John Dennis <jdennis@redhat.com>

  reply	other threads:[~2007-11-09  2:20 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 [this message]
2007-11-09 14:23         ` Steve Grubb
2008-01-07 13:21 ` Klaus Heinrich Kiwi
  -- 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=4733C3FA.9000005@redhat.com \
    --to=jdennis@redhat.com \
    --cc=Linux-audit@redhat.com \
    --cc=sgrubb@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