Hello,

I have an external hard drive for backups that keeps getting re-indexed by Nepomuk quite frequently. Since the backups are made daily, there are often new files on the drive, which I guess makes Nepomuk re-index the same files over and over again.

Since I have no interest in indexing my backed up files, is there any way to exclude the whole external drive from Nepomuk's indexing? Or just the backup folder, maybe?

is indexing of removable media enabled in systemsettings ?

No, it is disabled. Is Nepomuk also doing the indexing for Strigi? Or could it be that the "Indexing of removable media" setting only applies to Strigi, while Nepomuk doesn't care about that setting?

If mounted into the file system somewhere, make sure the removable device isn't mounted underneath a path directly indexed by Nepomuk (such as your $HOME, at least by default..)

I'm pretty sure it is not, since it is mounted under /media, but is there any command I can issue to check for symbolic links and such?

The following command should do the trick:

Code: Select all

find /path/to/directory -type l

I can't seem to find anything pointing to the external drive. I'll try to re-enable Nepomuk and see if I can figure out exactly what files it is indexing (if any) with lsof. Thanks for the suggestions so far!

Checking lsof gives away nepomukservices as reading files in a backup dir on the external drive, although there is nothing pointing to this directory on any other hard drive (as far as I can see). Could it be that the folders selected with the settings for Desktop Search only applies to the Strigi indexing and not the indexing of tags and comments by Nepomuk?

What is the full command for the offending process? The name has been shortened from "nepomukservicestub <something>".

Is the backup drive mounted under your $HOME by any chance?

The offending process is "nepomukservicestub nepomukfilewatch"

And no, the backup drive is not mounted under $HOME as far as I know.


(Sorry about the late reply. I have been busy with exams last week. And thanks a ton for helping me debug this!)

Please run the following command:

Code: Select all

mkdir -p $(kde4-config --localprefix)/Autostart
echo "sleep 2s && qdbus org.kde.NepomukServer /servicemanager stopService nepomukfilewatch &" > $(kde4-config --localprefix)/Autostart/kill-filewatcher.sh
chmod +x $(kde4-config --localprefix)/Autostart/kill-filewatcher.sh

There is a known bug about this which was filed several releases ago. The bug will get worse as more directories exist underneath your home directory. The above command sets up an autostart command which will disable the functionality which contains the bug. The functionality isn't too important.