From: Steve Grubb <sgrubb@redhat.com>
To: Aaron Lewis <the.warl0ck.1989@gmail.com>
Cc: "linux-audit@redhat.com" <linux-audit@redhat.com>
Subject: Re: Make the dispatcher run faster?
Date: Thu, 2 Jan 2014 09:37:50 -0500 [thread overview]
Message-ID: <20140102093750.714f6b43@ivy-bridge> (raw)
In-Reply-To: <CAJZVxRmKq1q-1Oc5SQ_K0Oyo672VesKo_sqJPdEBGGkR_v1HMA@mail.gmail.com>
On Thu, 26 Dec 2013 11:58:32 +0800
Aaron Lewis <the.warl0ck.1989@gmail.com> wrote:
> I've replaced the dispatcher with a self-written one, it only prints
> what it sees.
>
> Now I run auditd -f to make it stay foreground, and feed it with a
> massive amount of data,
>
> But the dispatcher prints one line for each second. Is there any speed
> limitation?
>
> If so, how do I change that
The audit daemon only keeps one event "in flight" until its consumed by
all sources. This is partly a limitation imposed by CC requirements
that loss of audit capability have a known limit on potentially lost
events. Generally it gets rid of events quickly.
One question to ask would be if auditd is writing to disk? If so, maybe
changing the writeback scheme would help. Besides that, you can change
the priority of auditd and/or the dispatcher.
-Steve
prev parent reply other threads:[~2014-01-02 14:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-26 3:58 Make the dispatcher run faster? Aaron Lewis
2014-01-02 14:37 ` 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=20140102093750.714f6b43@ivy-bridge \
--to=sgrubb@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