From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: "Kirkwood, David A" <DAVID.A.KIRKWOOD@saic.com>
Subject: Re: Chronological audit logs
Date: Tue, 28 Nov 2006 16:36:19 -0500 [thread overview]
Message-ID: <200611281636.20099.sgrubb@redhat.com> (raw)
In-Reply-To: <954E3479CC27224785179CA04904214D04336D07@0668-its-exmp01.us.saic.com>
On Tuesday 28 November 2006 16:06, Kirkwood, David A wrote:
> Can someone tell me how I can generate a chronological listing between 2
> dates of all the issues I have designated to watch in the audit capabilities
> of the system?
ausearch -ts date1 -te date2
> I currently use Sun workstations and generate the audit logs via praudit and
> was looking for some way to set up simaller archived weekly audit logs.
You would need to setup a cron job to do the weekly rotation if that is what
you want. There is a sample cron script, auditd.cron, that you can use as a
starting point. The normal rotation is by size in order to fit more data onto
your drives.
-Steve
prev parent reply other threads:[~2006-11-28 21:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 21:06 Chronological audit logs Kirkwood, David A
2006-11-28 21:20 ` Stephen Smalley
2006-11-28 21:36 ` 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=200611281636.20099.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=DAVID.A.KIRKWOOD@saic.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