public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: Logrotate and Audit Log Rotation
Date: Wed, 14 Nov 2012 08:54:13 -0500	[thread overview]
Message-ID: <8565226.qWSpgW3kEQ@x2> (raw)
In-Reply-To: <ba0db2f3-4cc0-e089-f33a-e5121538ba0d@me.com>

On Wednesday, November 14, 2012 12:52:31 PM Paul Whitney wrote:
> On RHEL 6 I am able to use the logrotate facility and compress logs using
> bzip2. However, when I try to use a similar method on RHEL 5, the auditd
> service fails to restart after the logrotate service rotates and compresses
> the rotated log file.
> 
> I found a post by Steve Grubb posted on 29 JUN 2011:
>   
> "Logrotate should not directly rotate the audit logs. I don't supply a
> logrotate  configuration, but if I did it would call service auditd rotate
> so that auditd performs the action. The audit daemon has to fulfill certain
> service guarantees that logrotate does not care about. For example, if the
> audit disk partition gets full, auditd can take the system down. Logrotate
> never will. So, you have to let auditd do its own thing or you will have
> some issues."
> 
> Is this still the case? 

Yes, it will always be the case. Logrotate does not understand the security 
requirements imposed by common criteria. You can either rotate on a cron job 
(an example script is shipped) or write a logrotate script that sends SIGUSR1 
to auditd.

-Steve

      reply	other threads:[~2012-11-14 13:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-14 12:52 Logrotate and Audit Log Rotation Paul Whitney
2012-11-14 13:54 ` Steve Grubb [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=8565226.qWSpgW3kEQ@x2 \
    --to=sgrubb@redhat.com \
    --cc=linux-audit@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox