Am Samstag, 20. Dezember 2014, 10:48:01 schrieb Martin Steigerwald: > Am Freitag, 19. Dezember 2014, 19:33:35 schrieb Volker Wysk: > > Hi! > > Hi Volker, > > > Is there a way to tell, what the baloo file indexer is doing in the > > background? It runs and runs, and I'm wondering, how much longer the > > indexing will take. > > Several ways: > > 1) Stop the baloo_file process and start it on a konsole tab, you see its > activity there then. A balooctl restart on a Konsole may do the trick as > well.
"balooclt restart" works fine. > 2) Run kdebugdialog and activate debug for baloo_file, then run tail -f > ~/.xsession errors – This works as well, it may need a restart of Ballo file > indexer tough. I get the messages on the console. > 3) With an running baloo_file process on the fly: > > strace -e stat -p $(pgrep baloo_file) 2>&1 | grep -v "share/baloo" > > if you want to see a bit more than use -e open Yes, this works. I can see which files are being indexed, by calling "strace -e trace=file -p ...". > So check whether a file is index you can try balooshow command: This works as well. Thanx for your help! Volker -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/3542039.iG84cROA4b@debian
