From: John McCutchan <ttb@tentacle.dhs.org>
To: nf2@scheinwelt.at
Cc: Chris Wedgwood <cw@f00f.org>,
nautilus-list@gnome.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC/PATCH] inotify -- a dnotify replacement
Date: Tue, 11 May 2004 08:24:42 -0400 [thread overview]
Message-ID: <1084278281.1225.15.camel@vertex> (raw)
In-Reply-To: <1084276364.4081.63.camel@lilota.lamp.priv>
On Tue, 2004-05-11 at 07:52, nf wrote:
> On Tue, 2004-05-11 at 04:47, Chris Wedgwood wrote:
> > On Mon, May 10, 2004 at 06:17:40PM -0400, John McCutchan wrote:
> >
> > > According to everyone who uses dnotify it is.
> >
> > I don't buy that. I have used dnotify and signals where not an issue.
> > Why is this an issue for others?
>
> I believe the worst thing about dnotify is the "umount blocking"
> behaviour. It drives me crazy since i use the Linux desktop. So if this
> is the "Year of the linux desktop", please please switch OFF dnotify
> until it does not open files for monitoring anymore! Or until "inotify"
> works.
>
> Btw, i have written a little tool to assist people with the
> umount-problem and collected some links
> http://www.scheinwelt.at/~norbertf/wbumount/.
That will be fixed with inotify.
>
> > > The idea is to encourage use of a user-space daemon that will
> > > multiplex all requests, so if 5 people want to watch /somedir the
> > > daemon will only use one watcher in the kernel. The number might be
> > > too low, but its easily upped.
> >
> > If you are to use a daemon for this, why no use dnotify?
>
> I don't understand, why the author of inotify wants to force people to
> use user-space daemons like fam (which requires xinetd, ...)? Does using
> a daemon for multiplexing really add efficiency? Is it really worth
> adding all the complexity of things like "fam" to the system, just
> because more than one application monitor the same directory once in a
> while? I doubt it.
>
I doesn't have to be fam. I am not sure if having a daemon is the best
way to go either, but I think that having a daemon (not necessarily fam)
could be beneficial. Beyond multiplexing you could keep a buffer of
events and try and combine some events before sending them to the apps.
But if it turns out that a daemon is not the best way, we can adjust the
limits set on the driver and everyone can just use it directly. So relax
I am not trying to force anything, it was just an idea.
John
next prev parent reply other threads:[~2004-05-11 12:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-10 1:35 [RFC/PATCH] inotify -- a dnotify replacement John McCutchan
2004-05-10 2:11 ` Chris Wedgwood
2004-05-10 22:17 ` John McCutchan
2004-05-10 22:31 ` Davide Libenzi
2004-05-10 22:41 ` John McCutchan
2004-05-10 22:52 ` Davide Libenzi
2004-05-10 23:10 ` Valdis.Kletnieks
2004-05-10 23:42 ` Davide Libenzi
2004-05-11 4:11 ` Chris Wedgwood
2004-05-11 2:00 ` Ian Kent
2004-05-11 2:47 ` Chris Wedgwood
2004-05-11 11:52 ` nf
2004-05-11 12:17 ` Stephen Rothwell
2004-05-11 12:24 ` John McCutchan [this message]
[not found] ` <1084278605.3839.47.camel@carados.180sw.com>
[not found] ` <1084885604.4062.48.camel@lilota.lamp.priv>
[not found] ` <1085127066.20393.440.camel@localhost.localdomain>
2004-05-21 12:04 ` nf
2004-05-11 12:20 ` John McCutchan
2004-05-11 12:46 ` viro
2004-05-11 19:02 ` John McCutchan
2004-05-11 20:28 ` carbonated beverage
2004-05-11 21:28 ` John McCutchan
2004-05-11 15:02 ` Alexander Larsson
2004-05-11 21:41 ` Chris Wedgwood
2004-05-12 12:38 ` Jörn Engel
2004-05-13 15:36 ` raven
2004-05-13 19:04 ` Chris Wedgwood
2004-05-14 7:04 ` Ian Kent
2004-05-13 21:24 ` John McCutchan
2004-05-14 2:02 ` Ian Kent
2004-05-15 4:52 ` raven
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=1084278281.1225.15.camel@vertex \
--to=ttb@tentacle.dhs.org \
--cc=cw@f00f.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nautilus-list@gnome.org \
--cc=nf2@scheinwelt.at \
/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