From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linda Knippers Subject: Re: Double addition of rule yields two log messages Date: Fri, 19 May 2006 15:28:18 -0400 Message-ID: <446E1C52.4070105@hp.com> References: <446DE295.8040503@us.ibm.com> <200605191429.18451.sgrubb@redhat.com> <446E12D1.2060709@hp.com> <200605191501.38031.sgrubb@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200605191501.38031.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 Steve Grubb wrote: > On Friday 19 May 2006 14:47, Linda Knippers wrote: > >>But why does ausearch care? > > Ausearch doesn't care about this particular setting. Its looking at the config > to find the log files. The parser is what cares and it is what emitted this > warning. But why is it even a warning of the freq value is only valid if flush is set to incremental? > As such, you can use ausearch to make sure your config is sane > before sending sighup to reconfigure the audit daemon. Sounds like an odd use of ausearch. >>Seems like if anything cared it would be the auditd but I can't find an >>error or warning from it anywhere. > > Should be in the syslog. I see it after doing a HUP and when doing an /etc/init.d/auditd restart but not when auditd starts at boot time. -- ljk