[Bug 115801] Re: max inotify user watches in the kernel should be increased

** Summary changed: - max inotify user watches in the kernel should be increased for beagle indexing to be optimal + max inotify user watches in the kernel should be increased -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://b

[Bug 115801] Re: max inotify user watches in the kernel should be increased for beagle indexing to be optimal

As an end user, i'm curious -- how was this addressed in procps 1:3.2.7-3ubuntu6? I'm still running into this hard limit in jaunty. -- max inotify user watches in the kernel should be increased for beagle indexing to be optimal https://bugs.launchpad.net/bugs/115801 You received this bug notific

[Bug 115801] Re: max inotify user watches in the kernel should be increased for beagle indexing to be optimal

** Changed in: beagle (Ubuntu) Status: New => Invalid -- max inotify user watches in the kernel should be increased for beagle indexing to be optimal https://bugs.launchpad.net/bugs/115801 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to U

[Bug 115801] Re: max inotify user watches in the kernel should be increased for beagle indexing to be optimal

This was addressed in procps 1:3.2.7-3ubuntu6 ** Changed in: procps (Ubuntu) Status: New => Fix Released -- max inotify user watches in the kernel should be increased for beagle indexing to be optimal https://bugs.launchpad.net/bugs/115801 You received this bug notification because you a

[Bug 115801] Re: max inotify user watches in the kernel should be increased for beagle indexing to be optimal

If an inotify watch isn't used, it uses no memory. So simply increasing the limit has no overhead on the system. It's only when they're used that they actually consume kernel memory. I don't know exactly how much is used, but I believe there's no additional overhead other than the inotify struct

[Bug 115801] Re: max inotify user watches in the kernel should be increased for beagle indexing to be optimal

I think max_user_watches should be set according on the system's RAM in the desktop distribution and kept at the low default for the server distribution. Does anybody actually know how much memory an inotify watch consumes? -- max inotify user watches in the kernel should be increased for beagl

[Bug 115801] Re: max inotify user watches in the kernel should be increased for beagle indexing to be optimal

I added procps to this as an affected package, because I think the right place to fix this is there. This can happen with any program that will set up lots of inotify watches, not just Beagle, although it's the most likely culprit at this point. I'd suggest setting it to at least 65536. A higher

[Bug 115801] Re: max inotify user watches in the kernel should be increased for beagle indexing to be optimal

This is possibly also the cause for bug #77106 -- max inotify user watches in the kernel should be increased for beagle indexing to be optimal https://bugs.launchpad.net/bugs/115801 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu.