public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Richard Guy Briggs <rgb@redhat.com>
To: Aaron Lewis <the.warl0ck.1989@gmail.com>
Cc: "linux-audit@redhat.com" <linux-audit@redhat.com>
Subject: Re: Clear kernel audit buffer?
Date: Mon, 13 Jan 2014 14:24:38 -0500	[thread overview]
Message-ID: <20140113192438.GC23577@madcap2.tricolour.ca> (raw)
In-Reply-To: <CAJZVxRkVZL0h8ugsEzRJo2U5LPq19OViRX1ovV208HwGhQkEWg@mail.gmail.com>

On 13/12/26, Aaron Lewis wrote:
> Hi,
> 
> I'm doing a stress test on auditd, so I add a rule to monitor "open"
> syscall, then I use a c program to generate massive amount of logs.
> The program finished and exited.
> 
> But I generated too much, if I kill auditd and start it again, I can
> still see a lot of type=SYSCALL logs. (But not CWD or PATH)
> 
> Can I clear the existing buffer?

Did you remove the rule that caused the massive amount of logging?

Auditd will drain that buffer.  The default is a queue of 64 messages,
which should drain reasonably quickly if the rule has been removed and
the queue length hasn't been overridden to a huge value.  Otherwise,
there is no other way to drain that buffer.

> Aaron Lewis - PGP: 0xDFE6C29E ( http://keyserver.veridis.com )

- RGB

--
Richard Guy Briggs <rbriggs@redhat.com>
Senior Software Engineer, Kernel Security, AMER ENG Base Operating Systems, Red Hat
Remote, Ottawa, Canada
Voice: +1.647.777.2635, Internal: (81) 32635, Alt: +1.613.693.0684x3545

  reply	other threads:[~2014-01-13 19:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-26  0:54 Clear kernel audit buffer? Aaron Lewis
2014-01-13 19:24 ` Richard Guy Briggs [this message]
2014-01-14  5:09   ` Aaron Lewis
2014-01-14 14:21     ` Steve Grubb
2014-01-14 14:47       ` Richard Guy Briggs

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=20140113192438.GC23577@madcap2.tricolour.ca \
    --to=rgb@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=the.warl0ck.1989@gmail.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