From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: aureport header question
Date: Wed, 31 Mar 2010 10:32:57 -0400 [thread overview]
Message-ID: <201003311032.57650.sgrubb@redhat.com> (raw)
In-Reply-To: <cecd18b01003251935g1c03449dn6e80f0929c374de5@mail.gmail.com>
On Thursday 25 March 2010 10:35:57 pm LC Bruzenak wrote:
> Now see the issue I was trying to illustrate earlier (ending time of
> range in logs; there are definitely events there in that timeframe) :
> [root@audit tmp]# aureport -if audit-mirror/ -i --summary -ts
> yesterday -te 03/26/2010 00:00:00
aureport/search aborts processing an event if the parsing is wrong. There may
be some records with formats that do not match. You might try getting the logs
smaller and smaller until you get a few that reproduce the problem.
> And this is the issue I was questioning.
> Do you think it has been addressed already by possibly newer code than
> I have (1.7.16)?
1.7.17 is the latest. I don't think it addresses this issue.
-Steve
prev parent reply other threads:[~2010-03-31 14:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 23:13 aureport header question LC Bruzenak
2010-03-26 1:49 ` LC Bruzenak
2010-03-26 2:35 ` LC Bruzenak
2010-03-31 14:32 ` Steve Grubb [this message]
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=201003311032.57650.sgrubb@redhat.com \
--to=sgrubb@redhat.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;
as well as URLs for NNTP newsgroup(s).