Re: Connector: Filesystem Events Connector v3

From: yang . y . yi
Date: Fri Mar 24 2006 - 09:17:30 EST


On 3/24/06, Arjan van de Ven <arjan@xxxxxxxxxxxxx> wrote:
> On Fri, 2006-03-24 at 11:08 +0300, Evgeniy Polyakov wrote:
> > On Thu, Mar 23, 2006 at 11:23:45PM -0800, Andrew Morton (akpm@xxxxxxxx)
> wrote:
> > > "David S. Miller" <davem@xxxxxxxxxxxxx> wrote:
> > > >
> > > > From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
> > > > Date: Fri, 24 Mar 2006 07:59:01 +0100
> > > >
> > > > > then make the syslog part optional.. if it's not already!
> > > >
> > > > Regardless I still think the filesystem events connector is a useful
> > > > facility.
> > >
> > > Why's that?
> > >
> > > (I'd viewed it as a fun thing, but I haven't really seen much pull for
> it,
> > > and the scalability issues in there aren't trivial).
> >
> > This module uses ratelimiting of event generation, so it will not hurt
> > performance, but probably this should be somehow tuned from userspace.
>
>
> .. so it has become unreliable for any kind of real use that depends on
> getting complete events. Such as virus scanning or updatedb etc
>
>
If there is such a use, that explains this connector is useful a bit,
ratelimiting is used to prevent DoS, audit also has such a feature,
you may take a look at it.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/