[Digikam-devel] [Bug 162535] startup is extremely slow when famd is running

Marcel Wiesweg marcel.wiesweg at gmx.de
Sat May 24 14:49:23 BST 2008

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

------- Additional Comments From marcel.wiesweg gmx de  2008-05-24 15:49 -------
Digikam is setting up a KDirWatch to monitor the directories it manages for added/removed files while it is running. That's all digikam is doing: Add a directory to the KDirWatch object.

KDirWatch from kdelibs can use different methods to watch files, one of them famd.

There has been a bug report about too many open file descriptors when using IIRC the inotify method, but I am not aware of a famd problem. Digikam is pushing the boundaries of dir watching by creating many watches, but from within digikam we cannot do too much about it. Kdelibs decides to use fam, and obviously this takes so much time. You can verify this by commenting out the three lines in digikam/albummanger.cpp containing "d->dirWatch->addDir"

More information about the Digikam-devel mailing list