From: LC Bruzenak <lenny@magitekltd.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: space_left_action
Date: Thu, 30 Jul 2009 16:12:26 -0500 [thread overview]
Message-ID: <1248988346.12117.688.camel@homeserver> (raw)
In-Reply-To: <200907301623.33057.sgrubb@redhat.com>
On Thu, 2009-07-30 at 16:23 -0400, Steve Grubb wrote:
> 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
Thanks for the info Steve!
I would think the manual resume option appropriate definitely for the
"suspend" option...but not really the syslog.
Is there a reason to not have it reset if the space is freed?
So if eventually I need to patch this, would you:
1: accept a change?
2: also want another parameter like "autoresume_on_space_free = false"
to preserve this behavior?
Thanks,
LCB.
--
LC (Lenny) Bruzenak
lenny@magitekltd.com
prev parent reply other threads:[~2009-07-30 21:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 20:13 space_left_action LC Bruzenak
2009-07-30 20:23 ` space_left_action Steve Grubb
2009-07-30 21:12 ` LC Bruzenak [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1248988346.12117.688.camel@homeserver \
--to=lenny@magitekltd.com \
--cc=linux-audit@redhat.com \
--cc=sgrubb@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.