[opensuse-kde] Strigi index not persistent
I recently upgraded my openSUSE 11.3 to KDE 4.6. I'm particularly interested in using desktop search etc., so the index created by Strigi is required (at least this is what i think...). After the upgrade, of course, the index had to be created, so i was patient. Some time later i rebooted the system after having checked that the Strigi indexer was indeed done with its work and idle. After the reboot i noticed that Strigi once again was running and busy indexing my huge media folder. Is this behavior normal? I'm 100% sure that no files were touched in the media folder, so i don't see any reason why Strigi should re-index the folder. Could it be that the index is not persistent and does not survive a system reboot? The running indexer does not particularly slow down my system, but still i'd like to know if there are some settings that i may need to adjust so that the index survives a restart. Thanks! Robert -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Monday 31 January 2011 15:31:17 Robert Graf-Waczenski wrote:
I recently upgraded my openSUSE 11.3 to KDE 4.6. I'm particularly interested in using desktop search etc., so the index created by Strigi is required (at least this is what i think...). After the upgrade, of course, the index had to be created, so i was patient. Some time later i rebooted the system after having checked that the Strigi indexer was indeed done with its work and idle.
After the reboot i noticed that Strigi once again was running and busy indexing my huge media folder.
Is this behavior normal? I'm 100% sure that no files were touched in the media folder, so i don't see any reason why Strigi should re-index the folder. Could it be that the index is not persistent and does not survive a system reboot?
The running indexer does not particularly slow down my system, but still i'd like to know if there are some settings that i may need to adjust so that the index survives a restart.
There's a distinction between scanning and indexing. Scanning is the process of looking for new and changed files (done by nepomuk's index module). Indexing is the extraction of characteristic metadata or fulltext for later searching (performed by the strigi indexing plugins). Unfortunately, due to the lack of recursive mtime (m = modification) in filesystems, desktop search tools have to scan the folders to be indexed on startup to identify any files that are new/changed while the desktop was logged out. If you have deep folder trees this can take a while. Then any new/changed files are passed to the indexer for [re]indexing. From the information you give, I think that the activity you noticed is nepomuk is scanning on login. As you say, this has very little impact on the system, because all the desktop search components are niced as far as possible. It could be improved by making the feedback clearer as to whether scanning for changes on startup or indexing changes is going on. HTH Will -- Will Stephenson, openSUSE Team SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
participants (2)
-
Robert Graf-Waczenski
-
Will Stephenson