From: Chris Friesen <cfriesen@nortelnetworks.com>
To: jcwren@jcwren.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel facilities for tracking file accesses
Date: Sun, 22 Jun 2003 00:09:36 -0400 [thread overview]
Message-ID: <3EF52C00.6080206@nortelnetworks.com> (raw)
In-Reply-To: 200306211845.41702.jcwren@jcwren.com
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?
Can't you just use strace against the daemon?
> I would prefer something
> that monitors the entire system, rather than trying to sandbox this
> particular program (it runs as a daemon).
How about the Linux Trace Toolkit?
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
prev parent reply other threads:[~2003-06-22 3:55 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 ` Kernel facilities for tracking file accesses J.C. Wren
2003-06-21 23:11 ` Samuel Thibault
2003-06-22 4:09 ` Chris Friesen [this message]
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=3EF52C00.6080206@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=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