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 12:46:03 -0500 [thread overview]
Message-ID: <1250531163.3048.720.camel@homeserver> (raw)
In-Reply-To: <OF9F4DBAA0.A11B45E7-ON85257615.005F5816-85257615.00605D58@us.ibm.com>
On Mon, 2009-08-17 at 13:32 -0400, David Flatley wrote:
> >> Lenny:
> >>
> >> I was going to move the rotated logs into /home/logs and use
> "ausearch
> >> -i -f /home/logs".
> >>
> >>
> >> David Flatley CISSP
> >>
> >>
>
> >David,
> >
> >It won't work like that; exactly the issue I described:
> >
> >[root@slim root]# mkdir logs-test
> >[root@slim root]# cd !$
> >cd logs-test
> >[root@slim logs-test]# auditctl -m "TEST message"
> >[root@slim logs-test]# service auditd rotate
> >Rotating logs: [ OK ]
> >[root@slim logs-test]# cp /var/log/audit/audit.log.1 .
> >[root@slim logs-test]# ausearch -i -f `pwd` -m USER
> ><no matches>
> >[root@slim logs-test]# grep TEST audit.log.1
> >node=slim type=USER msg=audit(1250529052.265:305135): user pid=8191
> >uid=0 auid=500 ses=4172 subj=user_u:user_r:user_t:s0 msg='TEST
> message:
> >exe="/sbin/auditctl" (hostname=?, addr=?, terminal=pts/18
> res=success)'
> >
> >
> >LCB.
>
> UGH this is a wrench in the works...
> I was hoping to grab all the rotated logs, process them while still
> allowing audit
> to run with no interruptions. Problem I run into is I run ausearch -i
> > /tmp/file and then
> do ausearch -i /nfs/file with auditd stopped, then compare files and
> if they are the same in
> size then delete the /tmp/file. I do this to make sure I get the log
> in the nfs archive directory
> and the /tmp is a backup if there is a problem. If audit is running
> there is no way the files will
> be equal in size while processing the /var/log/audit data in two
> different intervals.
It's a problem for me too.
I was thinking about just patching the ausearch code to behave as
desired...but hoping Steve beat me to it so there was a greatly reduced
chance of bad code...
:)
As for the archive issue, what I am planning is to make a snapshot of my
current audit log directory (technically the partition on which this
lives; that's another SECSCN issue), then rsync the snapshot over to a
backup server (via crossover network connection) and finally release the
snap mount. Then I do not have to compare file sizes ... and really the
size is only one indicator of correctness. You'd probably need a
checksum activity.
LCB.
--
LC (Lenny) Bruzenak
lenny@magitekltd.com
next prev parent reply other threads:[~2009-08-17 17:46 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
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 [this message]
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=1250531163.3048.720.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