From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: Duplicate audit event IDs
Date: Thu, 6 Apr 2006 11:06:02 -0400 [thread overview]
Message-ID: <200604061106.02733.sgrubb@redhat.com> (raw)
In-Reply-To: <60D45469A1AAD311A04C009027B6BF6805E38768@server20.inside.oracorp.com>
On Thursday 06 April 2006 10:47, Steve Brueckner wrote:
> What might cause this?
The event ID can be recycled. Its the combination of time stamp and serial
number that creates uniqueness.
> At some point my event IDs got reset (they didn't cycle that fast!). I've
> been playing quite a bit with the audit system so I'm not sure what caused
> it. Possibilities include:
>
> - Restarting the auditd service
Nope
> - Rebooting the machine
Yep
> - Deleting the /var/log/audit/audit.log file
Nope
There can also be wrapping.
> Or should this just plain not happen?
It can happen.
> I'm on FC4 using kernel 2.6.12-1.1447_FC4xen0. I'm afraid I can't easily
> upgrade at the moment because I've build an entire system predicated on old
> versions of SELinux and Xen.
You will likely have other problems on a kernel that old. I think 2.6.14 was
when we really had most features in place and stable.
> I also have a couple of other questions:
>
> - How large to audit event numbers get before they cycle back to zero?
I think its a u32 number.
> - Is there any way to have ausearch only the most recent audit log instead
> of all logs?
Sure, use the "-if" option and give it the full path to the file.
ausearch -if /var/log/audit/audit.log
-Steve
prev parent reply other threads:[~2006-04-06 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-06 14:47 Duplicate audit event IDs Steve Brueckner
2006-04-06 15:06 ` 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=200604061106.02733.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.