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: How to exclude a directory?
Date: Mon, 08 Sep 2014 12:50:33 -0400	[thread overview]
Message-ID: <1467823.yUMRrjSXbz@x2> (raw)
In-Reply-To: <CACv9p5oP=vxxmE5vK=Fnbzbo1EFc6U3rUaFmzHVRzbxT-tEoUQ@mail.gmail.com>

On Thursday, September 04, 2014 08:17:57 AM leam hall wrote:
> I'm looking for a way to not audit events in a directory tree. Is
> there such an option?

You should be able to put something near the top of your rules to do this. 
(Audit is a first rule to match wins system.)

-a never,exit -F dir=<full path to dir>

Note this only works on syscalls that contain a path as an argument. If the 
syscall triggering the event has an fd that was opened pointing into that 
directory, you will still get an event because the fd is not traced back to 
the device/inode each invocation.

-Steve

      reply	other threads:[~2014-09-08 16:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-04 12:17 How to exclude a directory? leam hall
2014-09-08 16:50 ` 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=1467823.yUMRrjSXbz@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