From mboxrd@z Thu Jan  1 00:00:00 1970
From: Steve Grubb <sgrubb@redhat.com>
Subject: Re: space_left_action
Date: Thu, 30 Jul 2009 16:23:32 -0400
Message-ID: <200907301623.33057.sgrubb@redhat.com>
References: <1248984834.12117.663.camel@homeserver>
Mime-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Return-path: <linux-audit-bounces@redhat.com>
In-Reply-To: <1248984834.12117.663.camel@homeserver>
Content-Disposition: inline
List-Unsubscribe: <https://www.redhat.com/mailman/listinfo/linux-audit>,
	<mailto:linux-audit-request@redhat.com?subject=unsubscribe>
List-Archive: <https://www.redhat.com/archives/linux-audit>
List-Post: <mailto:linux-audit@redhat.com>
List-Help: <mailto:linux-audit-request@redhat.com?subject=help>
List-Subscribe: <https://www.redhat.com/mailman/listinfo/linux-audit>,
	<mailto:linux-audit-request@redhat.com?subject=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 30 July 2009 04:13:54 pm LC Bruzenak wrote:
> 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.

Did you do a  "service auditd resume" ?

> 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?

You shouldn't need to restart it, but you should tell it to resume.

-Steve