From mboxrd@z Thu Jan 1 00:00:00 1970 From: LC Bruzenak Subject: space_left_action Date: Thu, 30 Jul 2009 15:13:54 -0500 Message-ID: <1248984834.12117.663.camel@homeserver> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from mx1.redhat.com (mx1.redhat.com [172.16.48.31]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n6UKED19015799 for ; Thu, 30 Jul 2009 16:14:13 -0400 Received: from mail.magitekltd.com (rrcs-24-242-137-197.sw.biz.rr.com [24.242.137.197]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n6UKDwBv023218 for ; Thu, 30 Jul 2009 16:13:58 -0400 Received: from [24.242.137.194] (helo=[192.168.30.40]) by mail.magitekltd.com with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1MWc0d-00020v-JN for linux-audit@redhat.com; Thu, 30 Jul 2009 15:13:51 -0500 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 List-Id: linux-audit@redhat.com Good news: When I set the space_left_action to syslog and crossed the boundary, I got a syslog message on the next audit event. Subsequent events did not generate any further syslog messages. Then I freed up disk space, sent in a few events for good measure (thinking it would reset the flag) and once again filled the disk past the threshold. Bad news: I didn't get the message again. Should this behavior have happened as I expected and another log message get into the messages log? Or as coded would the auditd need restart? Thx, LCB. -- LC (Lenny) Bruzenak lenny@magitekltd.com