From mboxrd@z Thu Jan 1 00:00:00 1970 From: leam hall Subject: Re: Audit log compression Date: Wed, 27 Jun 2018 13:14:52 -0400 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx1.redhat.com (ext-mx10.extmail.prod.ext.phx2.redhat.com [10.5.110.39]) by smtp.corp.redhat.com (Postfix) with ESMTPS id D6030309128B for ; Wed, 27 Jun 2018 17:15:05 +0000 (UTC) Received: from mail-wm0-f50.google.com (mail-wm0-f50.google.com [74.125.82.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 6A5EA5D5EE for ; Wed, 27 Jun 2018 17:14:54 +0000 (UTC) Received: by mail-wm0-f50.google.com with SMTP id p11-v6so6266262wmc.4 for ; Wed, 27 Jun 2018 10:14:54 -0700 (PDT) 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: linux-audit@redhat.com List-Id: linux-audit@redhat.com logrotate can be configured nicely. First big step is looking at what's going into the logs though. Are you logging at INFO level and do you need that. I've seen that be 90% or more of the log entries. On Wed, Jun 27, 2018 at 1:11 PM, Wyatt, Curtis R wrote: > What is the best/preferred method for compressing audit logs? > > I was thinking logrotate wouldn't work because auditd usually rotates it's > own logs and is smarter about rotating logs (I.e., based on log size as > opposed to having to wait before log rotate is kicked off). > > Thanks > > -- > Linux-audit mailing list > Linux-audit@redhat.com > https://www.redhat.com/mailman/listinfo/linux-audit