From: "J.C. Wren" <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 [thread overview]
Message-ID: <200306211845.41702.jcwren@jcwren.com> (raw)
In-Reply-To: <3EF4DCEF.7080708@yahoo.ca>
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
next prev parent reply other threads:[~2003-06-21 22:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-21 20:46 2.5.72 as VMware guest doesn't boot Peter Braam
2003-06-21 22:32 ` Jonathan Bastien-Filiatrault
2003-06-21 22:45 ` J.C. Wren [this message]
2003-06-21 23:11 ` Kernel facilities for tracking file accesses Samuel Thibault
2003-06-22 4:09 ` Chris Friesen
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=200306211845.41702.jcwren@jcwren.com \
--to=jcwren@jcwren.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®