Alan McKinnon writes: > If I reboot this machine and start KDE, Nepomuk starts a rather > long-lived index of my home directory. It takes up about 30-40% cpu > and lasts as much as 15 minutes sometimes. This is annoying because > after a reboot I usually want to catch up on mail, rss feeds and fire > up VirtualBox. So nepomuk is just wasting my time at this point. > > How does nepomuk know when to do it's thing, how can I tweak what it > does and how can I discover why it feels it necessary to reindex my > entire maildir when surely it has a perfectly valid index already from > just before I shut down?
I think it starts scanning everything over again at every login. I've been also annoyed by that, so I deactivated it, and activate it from time to time when I am away, so it won't bother me. Or you can have it active, and during login you can suspend Strigi's indexing by right-clicking on the Nepomuk/Strigi icon in the panel. You might be interested in this article that came up on the Planet KDE RSS feed yesterday: http://www.afiestas.org/nepomuk-is-not-fast-is-instant/ It suggests to set fs.inotify.max_user_watches to something quite large like 524288 via sysctl. I assume this is the number of directories being monitored with inotify, and if this is larger than the total number of directories, changes in a directory will be noticed at once. So maybe this will avoid the periodic scanning at all? I did not try this yet. But it won't stop the first scan after login. I think I will have to trim the list of directories to index. Currently, I selected my and another user's $HOME, and some data directories. This gives 666,000 files, which is probably a lot. So I guess I'll skip my MP3s, as they are indexed already by Amarok, and also those many directories with source code. Wonko
