linux-audit.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Bond Masuda <bond.masuda@jlbond.com>
To: Steve Grubb <sgrubb@redhat.com>, linux-audit@redhat.com
Subject: Re: audit log still getting rotated even with max_log_file_action = ignore?
Date: Fri, 6 Nov 2015 10:07:24 -0800	[thread overview]
Message-ID: <563CEC5C.5010301@jlbond.com> (raw)
In-Reply-To: <2015477.b7QVr7lf9X@x2>



On 11/02/2015 03:32 PM, Steve Grubb wrote:
> I took a quick look at the code. I can't see how this is happening
> unless auditd is receiving a SIGUSR1 signal. You might want to put
> some syslog calls in to auditd-event.c log when auditd gets told to
> rotate so that it can be correlated to other system activities. -Steve 

Hi Steve,

The cron script i mention below does use "service auditd rotate", which
does send a SIGUSR1. But these rotations are happening outside the time
frame when that cron job runs. Additionally, they seem to rotate around
when the log file reaches about 90MB. It almost seems like there's some
default behavior? I was wondering if maybe my syntax in the config file
was wrong and auditd was ignoring my setting and just using defaults?

Bond

>> I have a cron job in /etc/cron.daily/auditd that I use to rotate +
>> compress the audit logs, but this is not what is causing the audit log
>> rotation.
>>
>> Is there another setting I must set in order for it to not automatically
>> rotate the audit log? How do I achieve the desired effect, where the
>> audit log is only rotated when my cron script runs?

  reply	other threads:[~2015-11-06 18:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-02 21:40 audit log still getting rotated even with max_log_file_action = ignore? Bond Masuda
2015-11-02 23:32 ` Steve Grubb
2015-11-06 18:07   ` Bond Masuda [this message]
2015-11-06 19:12     ` Steve Grubb
2015-11-08  6:05       ` Bond Masuda

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=563CEC5C.5010301@jlbond.com \
    --to=bond.masuda@jlbond.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).