From: Yi Yang <yang.y.yi@gmail.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: [2.6.16 PATCH] Connector: Filesystem Events Connector
Date: Fri, 24 Mar 2006 08:45:09 +0800 [thread overview]
Message-ID: <44234115.7010303@gmail.com> (raw)
In-Reply-To: <1143101844.3147.9.camel@laptopd505.fenrus.org>
Arjan van de Ven wrote:
> On Wed, 2006-03-22 at 22:58 +0800, Yi Yang wrote:
>
>> This patch implements a new connector, Filesystem Event Connector,
>> the user can monitor filesystem activities via it, currently, it
>> can monitor access, attribute change, open, create, modify, delete,
>> move and close of any file or directory.
>>
>
>
> how is this not redundant functionality with the audit subsystem ?
>
If you open Audit option, audit subsystem will audit all the syscalls,
so it adds big overhead for the whole system,
but Filesystem Event Connector just concerns those operations related to
the filesystem, so it has little overhead,
moreover, audit subsystem is a complicated function block, it not only
sends audit results to netlink interface, but also
send them to klog or syslog, so it will add big overhead.
I think you can look File Event Connector as subset of audit subsystem,
but File Event Connector is a very lightweight
subsystem.
>
>
>
next prev parent reply other threads:[~2006-03-24 0:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 14:58 [2.6.16 PATCH] Connector: Filesystem Events Connector Yi Yang
2006-03-22 20:14 ` Serge E. Hallyn
2006-03-23 1:01 ` Yi Yang
2006-03-23 7:43 ` Matt Helsley
2006-03-23 8:52 ` Evgeniy Polyakov
2006-03-24 1:25 ` Yi Yang
2006-03-24 1:21 ` Yi Yang
2006-03-24 7:35 ` Matt Helsley
2006-03-24 8:11 ` Evgeniy Polyakov
2006-03-24 9:42 ` Matt Helsley
2006-03-24 10:09 ` Evgeniy Polyakov
2006-03-24 14:04 ` yang.y.yi
2006-03-24 2:50 ` [2.6.16 PATCH] " Yi Yang
2006-03-24 9:53 ` Matt Helsley
2006-03-23 8:17 ` Arjan van de Ven
2006-03-24 0:45 ` Yi Yang [this message]
2006-03-24 6:46 ` Arjan van de Ven
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=44234115.7010303@gmail.com \
--to=yang.y.yi@gmail.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--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