From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com, "Tangren, Bill" <bill.tangren@usno.navy.mil>
Subject: Re: questions about auditing on a new RH 6 box
Date: Fri, 14 Jan 2011 13:58:44 -0500 [thread overview]
Message-ID: <201101141358.44706.sgrubb@redhat.com> (raw)
In-Reply-To: <1295026506.2041.19.camel@lcb>
On Friday, January 14, 2011 12:35:06 pm LC Bruzenak wrote:
> Probably can use a sampling of events as well.
Since keys are not being used to classify events (hint hint) the best you can do is
run something like this:
aureport --start today --summary --syscall -i
-Steve
next prev parent reply other threads:[~2011-01-14 18:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 16:21 questions about auditing on a new RH 6 box Tangren, Bill
2011-01-14 16:42 ` Eric Paris
2011-01-14 17:23 ` Tangren, Bill
2011-01-14 17:35 ` LC Bruzenak
2011-01-14 17:56 ` Tangren, Bill
2011-01-14 18:39 ` LC Bruzenak
2011-01-14 19:04 ` Tangren, Bill
2011-01-14 18:10 ` Tangren, Bill
2011-01-14 19:12 ` Steve Grubb
2011-01-14 19:26 ` Tangren, Bill
2011-01-14 19:57 ` Steve Grubb
2011-01-14 18:58 ` Steve Grubb [this message]
2011-01-14 19:07 ` Tangren, Bill
2011-01-14 19:24 ` LC Bruzenak
2011-01-14 19:27 ` Tangren, Bill
2011-01-14 19:39 ` Steve Grubb
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=201101141358.44706.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=bill.tangren@usno.navy.mil \
--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