From: Hareesh Nagarajan <hnagar2@gmail.com>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Diego Calleja <diegocg@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Looking for a file monitor
Date: Fri, 24 Feb 2006 22:01:08 -0600 [thread overview]
Message-ID: <43FFD684.2020309@gmail.com> (raw)
In-Reply-To: <200602241949_MC3-1-B93F-2159@compuserve.com>
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.
Hareesh
next prev parent reply other threads:[~2006-02-25 4:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-25 0:46 Looking for a file monitor Chuck Ebbert
2006-02-25 4:01 ` Hareesh Nagarajan [this message]
2006-02-25 8:49 ` Arjan van de Ven
-- 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=43FFD684.2020309@gmail.com \
--to=hnagar2@gmail.com \
--cc=76306.1226@compuserve.com \
--cc=diegocg@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