https://bugs.kde.org/show_bug.cgi?id=437888
--- Comment #3 from tagwer...@innerjoin.org --- (In reply to Yuri from comment #2) > The only thing that I did - I installed kde5. It does whatever kde5 does by > default. If you could attach the .config/baloofilerc file, that should say what's happening. I do see that different distributions set up baloo indexing in different ways. > There is no need to keep files open in order to index them. Clear. What I see in Linux is that the "baloo_file" process makes a list of all the files that need indexing and, if content indexing is enabled, feeds batches of 40 files to the indexer process "baloo_file_extractor" to be read and indexed. "baloo_file" does however attempt to work out the Mime Type of the files - and this can require a 'peek' into the file if it is not clear from the the file extension. > It looks like baloo either leaks file descriptors, or keeps them referenced > for no good reason. I'm pretty sure I've have hit the same issue on Linux if there was a general problem. Googling says that "ulimit -n" shows the limit, this gives me 1024 and I have no trouble... -- You are receiving this mail because: You are watching all bug changes.
