From kde-commits  Mon Dec 05 16:36:12 2005
From: Stephan Kulow <coolo () kde ! org>
Date: Mon, 05 Dec 2005 16:36:12 +0000
To: kde-commits
Subject: Re: branches/KDE/3.5/kdelibs/kio/kio
Message-Id: <200512051736.15538.coolo () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-commits&m=113380055600363

Am Sonntag, 4. Dezember 2005 23:15 schrieb David Faure:
> On Wednesday 30 November 2005 21:41, Dirk Mueller wrote:
> > SVN commit 484448 by mueller:
> >
> > inotify support
> >
> >
> >  M  +45 -0     configure.in.in
> >  M  +271 -21   kdirwatch.cpp
> >  M  +1 -1      kdirwatch.h
> >  M  +15 -2     kdirwatch_p.h
>
> I tried testing it, but although inotify is available and detected as such,
> KDirWatch seems to prefer FAM above Inotify (addEntry says useFAM() before
> useINotify()). Is that intentional?
>
>
> (Here FAM means launching gam_server, which stats and stats and stats...
> Running strace -p on it shows that it's really fond of calling stat()...)
Mean! With "the real fam" you get a "connection failed" and we pick *notify. 
Now you have ganim and fam is started on demand - then again ganim will use
inotify is available. But as you did not recompile after updating your kernel,
it will fall back to stat.

As I see no way to differ between fam and ganim, I'm not sure what to prefer.
With fam, our policy was to prefer it if the user started the fam daemon. So I
guess inotify->fam->dnotify might be the best choice.

Greetings, Stephan