mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Hareesh Nagarajan <hnagar2@gmail.com>
Cc: Chuck Ebbert <76306.1226@compuserve.com>,
	Diego Calleja <diegocg@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Looking for a file monitor
Date: Sat, 25 Feb 2006 09:49:02 +0100	[thread overview]
Message-ID: <1140857342.2991.6.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <43FFD684.2020309@gmail.com>

On Fri, 2006-02-24 at 22:01 -0600, Hareesh Nagarajan wrote:
> Chuck Ebbert wrote:
> > In-Reply-To: <43FF3C1C.5040200@gmail.com>
> > 
> > On Fri, 24 Feb 2006 at 11:02:20 -0600, Hareesh Nagarajan wrote:
> > 
> >> But if we want to keep a track of all the files that are opened, read, 
> >> written or deleted (much like filemon; ``Filemon's timestamping feature 
> >> will show you precisely when every open, read, write or delete, happens, 
> >> and its status column tells you the outcome."), we can write a simple 
> >> patch that makes a note of these events on the VFS layer, and then we 
> >> could export this information to userspace, via relayfs. It wouldn't be 
> >> too hard to code a relatively efficient implementation.
> > 
> >  Doesn't auditing do all this?
> 
> I have no idea about auditing, but I would guess it internally uses inotify.


it doesn't; it uses the audit framework which, by the way, exactly does
what the proposed patch above would do :)



  reply	other threads:[~2006-02-25  8:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-25  0:46 Chuck Ebbert
2006-02-25  4:01 ` Hareesh Nagarajan
2006-02-25  8:49   ` Arjan van de Ven [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-02-24  7:51 Wei Hu
2006-02-24  8:06 ` Hareesh Nagarajan
2006-02-24  8:38   ` Wei Hu
2006-02-24 12:05   ` Diego Calleja
2006-02-24 17:02     ` Hareesh Nagarajan
2006-02-25  0:40       ` Wei Hu
2006-02-25  4:00         ` Hareesh Nagarajan
     [not found] ` <43FEC9EC.7080902@dawes.za.net>
2006-02-24 15:03   ` Wei Hu

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=1140857342.2991.6.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=76306.1226@compuserve.com \
    --cc=diegocg@gmail.com \
    --cc=hnagar2@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®