Date: Sat, 21 Jun 2003 19:11:36 -0400
From: Samuel Thibault <Samuel.Thibault@ens-lyon.fr>
To: "J.C. Wren" <jcwren@jcwren.com>
Cc: linux-kernel@vger.kernel.org, rdr@cs.unh.edu
Subject: Re: Kernel facilities for tracking file accesses
Message-ID: <20030621231136.GE650@bouh.unh.edu>
Reply-To: Samuel Thibault <samuel.thibault@fnac.net>
Mail-Followup-To: "J.C. Wren" <jcwren@jcwren.com>,
	linux-kernel@vger.kernel.org, rdr@cs.unh.edu
References: <20030621204615.GA32341@peter.cfs> <3EF4DCEF.7080708@yahoo.ca> <200306211845.41702.jcwren@jcwren.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200306211845.41702.jcwren@jcwren.com>
User-Agent: Mutt/1.4i-nntp
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 865
Lines: 20

On sat 21 jun 2003 18:45:41 GMT, J.C. Wren wrote:
> 	Does any facility exist in the 2.4 and up kernels for logging *every* open, 
> read, write, seek, close, etc call?

I'm currently working on Robert D. Russell's "Fast Kernel Tracing", see
his homepage http://www.cs.unh.edu/~rdr/ for the paper & distribution.
This is for kernel 2.4.0-test9, though.

The most recent version I'm working on is for 2.4.21, should support
on-the-fly log flushing and work on smp (not much tested though, it
began to work yesterday :) ). It might be ported to 2.5 without too
much work.

Hoping this might meet your needs,
Samuel Thibault
-
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/