https://bugs.kde.org/show_bug.cgi?id=505696
JMB9 <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from JMB9 <[email protected]> --- I thought "baloo" is an ill sevice which should be off by default - but at least I can swith that off in KDE settings ... Why is Inotify going crazy that way - and no warning presented. How can I revoke those bad things Inotify did when it increases the limit (3 times, I think - not sure - and still demanding the limit to be further increases!). It must severly disturb the kernel for such an extreme reaction - with 128 GB ECC memory! So like Baloo, Inotify and general file monitoring should never be started in that way and it should be asked if this is welcome with a warning about performance! And it is still crazy giving the same message: ~~ Inotify Instance Capacity Low You have too many applications wanting to monitor file changes! When the capacity is exhausted it will prevent further file monitoring from working correctly. Either close some applications or increase the limit. Currently using 90% of instances and 0% of watches. ~~ And I still wonder why any file should get monitored - this is no trusted system (i.e. hardened) and the only things monitored would bei root filesystem and memory for getting out of free space and causing some info that it is below ??%. But this is not done ... Any explanation what it is intended for and why it ruins a capable workstation that easy would be welcom. Especially how to revoce the ill things Inotify did so I can at least tests KDE 6 - I will work with the Kubuntu partition till KDE 6 is in a suitable situation like Debian Testing - currently KDE neon with KDE 6 is just unstable! -- You are receiving this mail because: You are watching all bug changes.
