From: Steve Grubb <sgrubb@redhat.com>
To: leam hall <leamhall@gmail.com>
Cc: linux-audit@redhat.com
Subject: Re: Current Red Hat Kernels 2.6.18 & 2.6.32 not able to have non-existent files in audit.rules?
Date: Tue, 2 Feb 2016 20:03:53 +0100 [thread overview]
Message-ID: <20160202200353.22b7e189@ivy-bridge> (raw)
In-Reply-To: <CACv9p5orRadb_KjYjz8H+OXrnyjBnSztzGJjb6bwKNyjO_YMpg@mail.gmail.com>
On Tue, 2 Feb 2016 12:05:38 -0500
leam hall <leamhall@gmail.com> wrote:
> Running into errors where we're pushing out a blanket audit.rules
> file and some servers don't have some of the files. I've seen the -i
> and -c suggestion for auditctl but wanted to confirm that that's the
> right choice. We need to ensure warnings don't choke auditd or make
> it skip other rules.
-c will make it continue but ultimately report failure.
-i will make it continue and pretend nothing is wrong.
Either could be correct depending on whether you want success or
failure final status.
-Steve
next prev parent reply other threads:[~2016-02-02 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 17:05 Current Red Hat Kernels 2.6.18 & 2.6.32 not able to have non-existent files in audit.rules? leam hall
2016-02-02 19:03 ` Steve Grubb [this message]
2016-02-02 19:12 ` leam hall
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=20160202200353.22b7e189@ivy-bridge \
--to=sgrubb@redhat.com \
--cc=leamhall@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