https://bugs.kde.org/show_bug.cgi?id=435383
--- Comment #9 from tagwer...@innerjoin.org ---
If you have not tried "strace", it is magic.
It shows you the system calls a process makes. That means you should be able to
see "baloo_file" finding and reading the indexed directories, asking for a
iNotify watch and being told when iNotify sees new or changed file. The logged
data is "somewhat obscure" and some guesses can be required to work out what is
happening but it could say where the indexing process is breaking.
What I've not found is a way of watching the second stage in the indexing, when
the file content is extracted (baloo_file makes a list of "everything needing
indexing", which can be a very quick process, and then asks
"baloo_file_extractor" to look at the content of each file)
When I've used it, I've killed the running copy of baloo_file and then run
strace -o baloo-strace.log baloo_file
from the command line.
Another other trick is "balooshow -x <file>", that looks up details of the
indexed file in the database. You can try looking up details for the file 'as
per' its actual folder and via the symlinked path. I get details when I try
both and also see "knows of" the Symlinked path:
$ balooshow -x Testdir/testfile.txt
3ffab0000fc01 64513 262059 Testdir/testfile.txt
[/home/test/Symlink/testfile.txt]
$ balooshow -x Symlink/testfile.txt
3ffab0000fc01 64513 262059 Symlink/testfile.txt
[/home/test/Symlink/testfile.txt]
--
You are receiving this mail because:
You are watching all bug changes.
