From mboxrd@z Thu Jan 1 00:00:00 1970 From: rshaw1@umbc.edu Subject: Re: Log rotation and client disconnects Date: Thu, 12 Aug 2010 11:16:51 -0400 (EDT) Message-ID: <45921.128.63.24.134.1281626211.squirrel@webmail.umbc.edu> References: <56567.128.63.24.134.1281373190.squirrel@webmail.umbc.edu> <201008091353.32210.sgrubb@redhat.com> <58805.128.63.24.134.1281621749.squirrel@webmail.umbc.edu> <201008121025.59525.sgrubb@redhat.com> 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.14]) by int-mx08.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id o7CFH1QK004970 for ; Thu, 12 Aug 2010 11:17:01 -0400 Received: from mx2.umbc.edu (mx2.umbc.edu [130.85.25.77]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o7CFGq68009294 for ; Thu, 12 Aug 2010 11:16:52 -0400 Received: from smtp.umbc.edu (localhost [127.0.0.1]) by umbc.edu (mx2.umbc.edu) with ESMTP id o7CFGptg024793 for ; Thu, 12 Aug 2010 11:16:51 -0400 (EDT) Received: from webmail.umbc.edu (webmail1.umbc.edu [130.85.24.52]) by smtp.umbc.edu (mx2-relay.umbc.edu) with ESMTP id o7CFGpEB024790 for ; Thu, 12 Aug 2010 11:16:51 -0400 (EDT) In-Reply-To: <201008121025.59525.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: linux-audit@redhat.com List-Id: linux-audit@redhat.com > On Thursday, August 12, 2010 10:02:29 am rshaw1@umbc.edu wrote: >> I've discovered the issue since I sent it, anyway. If num_logs is set >> to >> 0, auditd will ignore explicit requests to rotate the logs. I guess >> this >> may be intentional, but it's unfortunate as num_logs caps at 99 and I >> need >> to keep 365 of them. > > Have you looked at the keep_logs option for max_log_file_action? I did, but the man page states that keep_logs is similar to rotate, so it sounds like if I used this option, it would still rotate the log file if it went above the max_log_file size, which I don't want to happen. I suppose I could just set max_log_file to 99999 or something (if that's supported). Typically, uncompressed log files for ~400 clients on the central server end up being around 3-4Gb. Thanks for all the help so far; I think I'm almost there. --Ray