Subject: Re: Looking for a file monitor
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>
In-Reply-To: <43FFD684.2020309@gmail.com>
References: <200602241949_MC3-1-B93F-2159@compuserve.com>
	 <43FFD684.2020309@gmail.com>
Content-Type: text/plain
Date: Sat, 25 Feb 2006 09:49:02 +0100
Message-Id: <1140857342.2991.6.camel@laptopd505.fenrus.org>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1215
Lines: 28

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 :)


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/