From: "J.C. Wren" <jcwren@jcwren.com>
Reply-To: jcwren@jcwren.com
To: linux-kernel@vger.kernel.org
Subject: Kernel facilities for tracking file accesses
Date: Sat, 21 Jun 2003 18:45:41 -0400
User-Agent: KMail/1.5.2
References: <20030621204615.GA32341@peter.cfs> <3EF4DCEF.7080708@yahoo.ca>
In-Reply-To: <3EF4DCEF.7080708@yahoo.ca>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200306211845.41702.jcwren@jcwren.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 932
Lines: 20

	Does any facility exist in the 2.4 and up kernels for logging *every* open, 
read, write, seek, close, etc call?  I'm trying to debug a problem in a 
package I don't have source to, and I'm trying to prove that it's not 
applying a configuration path option to files it's opening.  

	Ideally, I'd like a kernel module I can load that I can apply a regexp or 
limited pattern matchng to, and will log a selected group of operations as 
defined by a bitmask or other configuration option.  I would prefer something 
that monitors the entire system, rather than trying to sandbox this 
particular program (it runs as a daemon).

	Do the kernels have facilties for such tracking?

	--John

-
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/