On 04/27/2014 04:57 AM, Lars Kruczynski wrote:
I have to say, that for a non-beta release of KDE...it's quite perplexing that baloo made it through all the betas and ended up like it is now. If I can catch it doing buggy things within minutes of using it, it makes one start wondering if they really tried it very much with large 1-3 TB drives 100% full of files, and running torrents, BOINC, etc.
What are these betas you were referring to? I've been keeping up with the KDE4 channel and I never saw a single instance of any betas available that included Baloo. Also, It would be nice if we could read the manual, (what manual!!!???), but not a shred of documentation came with baloo. If you look into baloofilerc you will see that you can exclude file types, and directories from indexing. It seems that excluding huge binary files like iso files and entire directories that are in use by bittorrent would be the solution to your problem. Remember there was a word of warning about the fact that it indexes your entire home directory unless you put in exclusions. In my case I excluded directories that contained my Virtual Machine disk image files. That criticism notwithstanding, I am NOT seeing any huge disk IO or cpu loading issues, even as I recompile entire subsystems with many many files. I think your issue is one of tuning. -- Explain again the part about rm -rf / -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org