From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: Make the dispatcher run faster? Date: Thu, 2 Jan 2014 09:37:50 -0500 Message-ID: <20140102093750.714f6b43@ivy-bridge> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: Aaron Lewis Cc: "linux-audit@redhat.com" List-Id: linux-audit@redhat.com On Thu, 26 Dec 2013 11:58:32 +0800 Aaron Lewis 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