From: John Jasen <jjasen@gmail.com>
To: linux-audit@redhat.com
Subject: Re: Auditd syslog plugin
Date: Mon, 4 Jun 2018 19:32:51 -0400 [thread overview]
Message-ID: <4a7bb53d-d76e-db82-b36d-50b693753afc@gmail.com> (raw)
In-Reply-To: <2348690.m2sBkKRHdC@x2>
If you're on a system using rsyslog, you can also leverage imfile and
send it directly to a remote logserver.
rsyslog event queuing also handles interruptions in remote logging more
gracefully than audispd syslog.
On 06/04/2018 06:11 PM, Steve Grubb wrote:
> On Monday, June 4, 2018 9:02:04 AM EDT Boyce, Kevin P [US] (AS) wrote:
>> All,
>>
>> After enabling the syslog plugin for audispd and sending logs to a remote
>> server I am seeing every event being written to /var/log/messages locally
>> which is filling up /var.
>>
>> This is all redundant since local audit logs are kept in /var/log/audit.
>> Is there a way to prevent auditd syslog plugin from writing to
>> /var/log/messages?
> That is pretty much what the plugin does. It writes all events to syslog
> which based on rules in /etc/rsyslog.conf decides what to do with the text.
> Typically it is to write everything to /var/log/messages.
>
> However, you can assign a specific facility to the audit events in the /etc/
> audisp/plugins.d/syslog.conf file and then in rsyslog.conf exclude the
> facility by putting <facility>.none on the /var/log/messages line.
>
> -Steve
>
>
> --
> Linux-audit mailing list
> Linux-audit@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-audit
prev parent reply other threads:[~2018-06-04 23:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 13:02 Auditd syslog plugin Boyce, Kevin P [US] (AS)
2018-06-04 22:11 ` Steve Grubb
2018-06-04 23:32 ` John Jasen [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=4a7bb53d-d76e-db82-b36d-50b693753afc@gmail.com \
--to=jjasen@gmail.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