https://bugs.kde.org/show_bug.cgi?id=433204
--- Comment #14 from Peter Wibberley <p.wibber...@btinternet.com> --- (In reply to Harald Sitter from comment #13) The thing I don't understand is that, up until 17 December, I would have had max_user_watches set at 8192 with the number of files not being significantly less than the current number, and it was working OK. Now, even a 16-fold increase in the value doesn't seem to make any difference. Hence I was wondering whether the problem could have been related to updates. >From my perspective, my problem is getting more diagnostic information. Thanks and regards > (In reply to Jonathan Riddell from comment #10) > > I wonder if this should be built into baloo rather than being distro > > specific > > It will sort itself with kernel 5.11. Well, to a degree. > > If my maths is correct linux 5.11 sets the watch limit to > 32G ~> 260k > 16G ~> 130k > 8G ~> 65k > 4G ~> 30k > > So this can conceivably still be easily exhausted. e.g. the original > reporter would need to have >16G or manually set the watch limit to track > their 200k files. > > As I've said, the UX is fairly weak since we don't inform the user when they > run out of inotify capacity. KDirWatch has the similar problem really > (albeit more with instances than watches). -- You are receiving this mail because: You are watching all bug changes.
