From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Booth Subject: Re: Events lost with dispatcher Date: Wed, 07 Apr 2010 13:44:08 +0100 Message-ID: <4BBC7E18.7080004@redhat.com> References: <28B815FA-A40A-4864-8268-79FA1D5223C6@gmail.com> <201003311548.35428.sgrubb@redhat.com> <201003311556.34422.sgrubb@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <201003311556.34422.sgrubb@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: Steve Grubb Cc: linux-audit@redhat.com List-Id: linux-audit@redhat.com On 31/03/10 20:56, Steve Grubb wrote: > Wait, you are writing a dispatcher...are you boosting your priority above > auditd? If not, you should probably increase it by at least 4. Your dispatcher > has to stay ahead of auditd. On a related note, has there been any more thought about loading dispatchers into auditd itself as dynamic libraries? This would solve this problem, and also the issue of accidentally writing a rule which is triggered by a dispatcher, causing a DOS. Matt -- Matthew Booth, RHCA, RHCSS Red Hat Engineering, Virtualisation Team M: +44 (0)7977 267231 GPG ID: D33C3490 GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490