From: LC Bruzenak <lenny@magitekltd.com>
To: David Flatley <dflatley@us.ibm.com>
Cc: linux-audit@redhat.com
Subject: Re: buffer space
Date: Mon, 17 Aug 2009 11:52:52 -0500 [thread overview]
Message-ID: <1250527972.3048.693.camel@homeserver> (raw)
In-Reply-To: <OF38D7A3B6.53926BC4-ON85257615.00596C69-85257615.005B61DB@us.ibm.com>
On Mon, 2009-08-17 at 12:38 -0400, David Flatley wrote:\
>
> I am in error, I meant space_left_action because there is an exec for
> this.
> I was going to do the "service auditd rotate" then move all the
> audit.log.* to
> another directory so that ausearch -i and aureport -i could run on the
> logs.
David,
I do not think this is entirely accurate.
It is one of my own issues. I am doing the same type thing.
This is necessary on a system with large amounts of audit data (as
aggregated systems tend to be).
I am also moving stuff out of the standard directory.
However, IIUC, the ausearch options will only work on specific files.
If you move the rotated files off to another directory you will lose the
ability to search the directory with a single ausearch command. If there
were a "-id" option (input directory, or similar) which allowed this I
believe it would work better.
Otherwise you could possibly cat the files into one large one, but this
is not optimal IMHO.
Steve recently patched the disk threshold code to auto-reset, which is
nice. You probably want this; it sounds as if we are doing similar
functions. I also have SECSCN issues/mitigations.
LCB.
--
LC (Lenny) Bruzenak
lenny@magitekltd.com
next prev parent reply other threads:[~2009-08-17 16:52 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 14:56 buffer space David Flatley
2009-08-13 15:29 ` Matthew Booth
2009-08-13 18:28 ` Steve Grubb
2009-08-17 14:49 ` David Flatley
2009-08-17 15:07 ` Steve Grubb
2009-08-17 15:36 ` Norman Mark St. Laurent
2009-08-17 16:38 ` David Flatley
2009-08-17 16:52 ` LC Bruzenak [this message]
2009-08-17 17:06 ` David Flatley
2009-08-17 17:15 ` LC Bruzenak
2009-08-17 17:24 ` LC Bruzenak
2009-08-17 21:18 ` David Flatley
2009-08-17 17:32 ` David Flatley
2009-08-17 17:46 ` LC Bruzenak
2009-08-17 18:01 ` Steve Grubb
2009-08-17 18:13 ` Norman Mark St. Laurent
2009-08-17 18:14 ` LC Bruzenak
2009-08-17 18:46 ` Norman Mark St. Laurent
2009-08-17 19:37 ` Steve Grubb
2009-08-17 19:46 ` Norman Mark St. Laurent
2009-08-18 13:02 ` David Flatley
2009-08-18 15:09 ` LC Bruzenak
2009-08-18 15:53 ` Steve Grubb
2009-08-27 17:21 ` David Flatley
2009-08-27 17:32 ` Steve Grubb
2009-08-27 17:45 ` David Flatley
2009-08-27 18:45 ` Steve Grubb
2009-08-27 17:33 ` LC Bruzenak
2009-08-23 4:12 ` D.A. Muran-de Assereto
2009-08-17 15:34 ` Norman Mark St. Laurent
2009-08-17 16:58 ` Mike Nixon
2009-08-23 4:32 ` David Muran-de Assereto
2009-08-23 16:12 ` Mike Nixon
2009-08-23 20:24 ` David Muran-de Assereto
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=1250527972.3048.693.camel@homeserver \
--to=lenny@magitekltd.com \
--cc=dflatley@us.ibm.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