All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Sawhill <rsawhill@redhat.com>
To: "warron.french" <warron.french@gmail.com>
Cc: linux-audit@redhat.com
Subject: Re: auditd.cron
Date: Thu, 23 Mar 2017 10:45:25 -0400	[thread overview]
Message-ID: <CAEkAO+xUNsk9zm0kD-CyK_eiR-xXcMia9n15StarWwEExJ0Vxg@mail.gmail.com> (raw)
In-Reply-To: <CAJdJdQk5oOLRHPsyJLbcGqzFy02uavgoKJh415QtrMLbMGbxgA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1269 bytes --]

On Wed, Mar 22, 2017 at 5:19 PM, warron.french <warron.french@gmail.com>
wrote:

> So, I needed a feature over 8 months ago, nobody could provide one for the
> following:
>        Rolling log files either when they hit a certain size or the day
> changed over at midnight.
>
> I know that I could have rolled the files at a specific size, by using the
> *max_log_file* attribute as identified in the */etc/audit/auditd.conf*,
> but there was no "builtin" for managing auto rotation at the start of a new
> day (0000 hrs).
>
> It looks like there is a file called */usr/share/doc/auditd-<**version>*
> */auditd.cron*
>
> *.*
> To me*, *this file is new; considering I needed it 8 months ago.
>
> *Anyway, how is this file implemented? * Simply move it to a directory
> with permissions to execute; ensure it is executable and then simply set up
> a cronjob to execute it at whatever time of day that I wish?
>
> *Finally, if I have '-e 2' as the last control in the audit.rules file;
> will the auditd.cron which executes as service auditd rotate still function
> properly?*
>


Steve covered the important parts, but for more hand-holding:

How to implement audit log rotation with compression based on time instead
of size <https://access.redhat.com/solutions/661603>

[-- Attachment #1.2: Type: text/html, Size: 2136 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



      parent reply	other threads:[~2017-03-23 14:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-22 21:19 auditd.cron warron.french
2017-03-22 21:48 ` auditd.cron Steve Grubb
2017-03-23 13:28   ` auditd.cron Ed Christiansen MS
2017-03-23 13:53     ` auditd.cron Simon Sekidde
2017-03-23 16:11       ` auditd.cron Steve Grubb
2017-03-23 14:45 ` Ryan Sawhill [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=CAEkAO+xUNsk9zm0kD-CyK_eiR-xXcMia9n15StarWwEExJ0Vxg@mail.gmail.com \
    --to=rsawhill@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=warron.french@gmail.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.