From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: audit 1.2.7 released Date: Wed, 20 Sep 2006 15:40:52 -0400 Message-ID: <200609201540.52990.sgrubb@redhat.com> References: <200609182013.40133.sgrubb@redhat.com> <200609201519.47804.sgrubb@redhat.com> <451195CB.9000909@hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <451195CB.9000909@hp.com> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: Paul Moore Cc: linux-audit@redhat.com List-Id: linux-audit@redhat.com On Wednesday 20 September 2006 15:26, Paul Moore wrote: > > I try very hard to not have any memory allocations in the audit system to > > prevent any possible failure due to fragmentation or leaks. I need to cap > > the buffer size at something to meet this design goal. > > If this buffer limitation results in the loss or partial-loss of an > audit record is there some notification sent? No. > This seems like an excellent way for an individual to obscure their actions > on a system. Well, the particular buffer that Amy cited was 128 in size and only for startup/shutdown messages. It has been increased to 384. The other buffer that holds the events from syscall, file system, and trusted apps was 8460 and is now 8970. -Steve