All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sankarshan Mukhopadhyay <sankarshan.mukhopadhyay@gmail.com>
To: pbriggs@ll.mit.edu
Cc: linux-audit@redhat.com
Subject: Re: "Watch"ing a directory
Date: Wed, 22 Aug 2007 20:10:11 +0530	[thread overview]
Message-ID: <46CC4ACB.8020904@gmail.com> (raw)
In-Reply-To: <1187792258.3151.108.camel@prudence.llan.ll.mit.edu>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Pete Briggs wrote:
> Is there any way to put a watch on a directory, so that an audit record
> will be generated if anyone cd's to that directory. I've tried things
> like:
> 
> -w /etc/audit/ -k ACCESS_AUDIT
> 
> but the rule never seems to get invoked. I'm running FC7 with
> audit-1.5.3

Let me add to this question ? Is it feasible to watch a top level
directory recursively ? ie say /opt and not /opt/mydir/mymoredir/ etc ?




- --

You see things; and you say 'Why?';
But I dream things that never were;
and I say 'Why not?' - George Bernard Shaw
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFGzErKXQZpNTcrCzMRAg3RAJ9x665sUBd5hzRjdX3x/g3bGdk6eACgpQn9
Wueth9+1jtrA+1S/za0qsgY=
=qowH
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2007-08-22 14:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-21 15:13 Auditing failed kill events Henning, Arthur C. (CSL)
2007-08-21 15:50 ` Steve Grubb
2007-08-21 17:50   ` Henning, Arthur C. (CSL)
2007-08-21 18:16     ` Steve Grubb
2007-08-21 21:19       ` Henning, Arthur C. (CSL)
2007-08-22 14:17         ` "Watch"ing a directory Pete Briggs
2007-08-22 14:36           ` Steve Grubb
2007-08-22 15:40             ` Pete Briggs
2007-08-22 16:03               ` Steve Grubb
2007-08-22 20:37             ` Wieprecht, Karen M.
2007-08-22 14:40           ` Sankarshan Mukhopadhyay [this message]
2007-08-22 14:59             ` Steve Grubb
2007-08-22 15:03               ` Eric Paris
2007-08-22 15:05               ` Ameel Kamboh
2007-08-22 16:09                 ` Steve Grubb
2007-08-22 20:16                   ` Ameel Kamboh

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=46CC4ACB.8020904@gmail.com \
    --to=sankarshan.mukhopadhyay@gmail.com \
    --cc=linux-audit@redhat.com \
    --cc=pbriggs@ll.mit.edu \
    /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.