[plasmashell] [Bug 520182] Provide more details for the Inotify Instance / Watch Capacity Low notification from the kde-inotify-survey
https://bugs.kde.org/show_bug.cgi?id=520182 --- Comment #3 from Murz --- Actually, there are a lot of apps that can "eat" inotify watchers a lot. For example, when opening a directory in VS Code, it can easily add 1 file watchers at once, which will significantly slow down the system. And if we have multiple VS Code windows, we want to understand which exact window triggers the issue. And it is great that KDE monitors this and informs the user about the issue. But then, users have to identify which exact app caused the issue, to resolve it correctly. Actually, without `kde-inotify-survey` tool, I see no other easy ways to identify the specific app that is causing the problem, that can be used by regular users without grep-wc-awk magic, and other bash-based scripts usually take a lot more time to gather the information. So, if we have `kde-inotify-survey` already in place, it would be awesome to make it more user-friendly! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 520182] Provide more details for the Inotify Instance / Watch Capacity Low notification from the kde-inotify-survey
https://bugs.kde.org/show_bug.cgi?id=520182 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL CC||[email protected] --- Comment #2 from David Edmundson --- >But the root cause of this notification is some application that uses too much >inotify watchers Kind of. In our case it's always baloo. Or another file indexer. Historically some distros had a low default of ~8000, now most raise it to a high default. I don't know about kubuntu. On Arch it's 524288 This notification was mostly to work around that. --- I don't think surfacing this in the notification helps anyone, it's such a low-level detail. If you know what an inotify watcher is, you know how to find this information out. There isn't actually much overhead to an inotify watcher, so what problem are we really solving? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 520182] Provide more details for the Inotify Instance / Watch Capacity Low notification from the kde-inotify-survey
https://bugs.kde.org/show_bug.cgi?id=520182 --- Comment #1 from Murz --- By the way, maybe it's better to provide a sensor with inotify usages and limits to track the values using a more standard way, instead of the custom implementation based on the `kde-inotify-survey` tool? Using sensors, we can build widgets, charts, and automation based on the values in the System Monitor and other tools directly. -- You are receiving this mail because: You are watching all bug changes.
