Hi,

I would like to know how KDE watches changes, using inotify?
Is it still using gamin?

I've found kdirwatch as service of nepomuk. Does this have a function??

Stef

actually i have the same problem here and hope some one help Us

andrawisnaser wrote:actually i have the same problem here and hope some one help Us

Can you describe your problem?? More than "same problem"??

If you are referring to the "nepomukservicestub filewatcher" component, then it is not responsible for the watching of directories and files by KDE itself. It merely exists to assist Nepomuk in keeping it's database up to date when files are moved.

More than often unfortunately it is abusive to the system - especially if you have a large number of source files under your $HOME directory.

Ok, so the nepomuk service filewatcher component does not do watch the underlying fs for filesystem watch purposes, and forward these to clients.

But then what is?

I've found some notify code in kde, as well in qt, like

qfilesystemwatcher.h.


Stef

Each KDE Process undertakes the watching of the files it needs to watch itself. They can use either QFileSystemWatcher, or KDirWatch. Both use inotify I believe.

Ah!

Thank you for replying. I already guessed something like that.
But gamin is still an optional requirement for kdelibs.

And when I test with the session gamin server and a client, like dolphin, I see that a FAM connection is still used.

I'm very interested in making inotify work with "outside of VFS" filesystems like cifs and FUSE filesystems. Inotify works perfectly, but only for local filesystems, without "unknown" backends like network filesystems and FUSE fs's.

I'm missing this in Linux, and am thinking how to solve this. I'm a FUSE fs writer, but the kernel is something still mysterious...

Anyway, thanks,

Stef

I would suggest in this case talking to the kernel developers about this, as they'll be the ones more knowledgable about it.