From: john slee <indigoid@higherplane.net>
To: Yasunori GOTO <y-goto@jp.fujitsu.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: file access log
Date: Thu, 9 Aug 2001 21:11:23 +1000 [thread overview]
Message-ID: <20010809211123.A3197@higherplane.net> (raw)
In-Reply-To: <0GHS003EV4XX9D@fjmail504.fjmail.jp.fujitsu.com>
In-Reply-To: <0GHS003EV4XX9D@fjmail504.fjmail.jp.fujitsu.com>
On Thu, Aug 09, 2001 at 11:45:00AM +0900, Yasunori GOTO wrote:
> I want to make the function which check the file access
> (create(), unlink(), and rename(), etc.)
> and take the log.
there are many applications for this sort of kernel interface. sgi have
an implementation of it called imon, but the patches don't seem to be
maintained anymore.
what sort of interface were you considering? my first impression was to
create something similar to route sockets, but i'm not really a kernel
hacker... i believe imon+fam used something like this but also using
fcntl() hacks, which to me seems a bit ugly... anyone want to correct
me? :-/
j.
--
"Bobby, jiggle Grandpa's rat so it looks alive, please" -- gary larson
prev parent reply other threads:[~2001-08-09 11:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-09 2:45 file access log Yasunori GOTO
2001-08-09 11:11 ` john slee [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=20010809211123.A3197@higherplane.net \
--to=indigoid@higherplane.net \
--cc=linux-kernel@vger.kernel.org \
--cc=y-goto@jp.fujitsu.com \
/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