If the kernel won't fix it, then this is a bug in tracker
** Changed in: tracker (Ubuntu)
Status: Invalid = Confirmed
--
tracker doesn't leave any for the rest of the class
https://bugs.launchpad.net/bugs/158040
You received this bug notification because you are a member of Ubuntu
Bugs,
tracker (0.6.4) leaves 500 inotify watches free - is that enough?
--
tracker doesn't leave any for the rest of the class
https://bugs.launchpad.net/bugs/158040
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
marking as fixed in 0.6.4
** Changed in: tracker (Ubuntu)
Status: Confirmed = Fix Released
--
tracker doesn't leave any for the rest of the class
https://bugs.launchpad.net/bugs/158040
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The ring-buffer approach is not going to be accepted. First off, a list
of files that have changed is useless. The full path does not accomodate
symlinks or hardlinks. Secondly, we don't want users being able to see
all the files that have changed. That's a data leak that exposes
security
Unlikely a fix would be applied to 2.6.22/gutsy even if one was
developed.
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: Jamie McCracken (jamiemcc-blueyonder) = (unassigned)
Status: New = Won't Fix
--
tracker doesn't leave any for the rest of the class
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team)
Status: New = Triaged
--
tracker doesn't leave any for the rest of the class
Workaround instructions to put it in a bootscript. Place
fs.inotify.max_user_watches=2
in /etc/sysctl.conf
Just For Info
--
tracker doesn't leave any for the rest of the class
https://bugs.launchpad.net/bugs/158040
You received this bug notification because you are a member of Ubuntu
Jamie,
That sounds great! I've been pretty peeved about inotify:s lack of
built-in recursive directory monitoring. A ring buffer of all file
changes would solve that one automatically... and the max_user_watches
problem to boot. :)
Only hope you can get it accepted upstream...
(this would
Confirmed here too. I spent a few hours trying to solve an issue whereby
one of my development projects that uses inotify couldn't add new
watches. I checked the maximum limits but couldn't find a way to get
inotify to report a list of the watches so in the end gave up on it.
Like Scott I have a
The quick fix is to increase number of inotify watch limit by default to
64,000 or something high
this should be a bug against the kernel or boot config though rather
than tracker
short term fix :
echo 65565 /proc/sys/fs/inotify/max_user_watches
long term: apply to a boot up script
For
Jamie: this isn't an invalid bug -- as you point out, it's either a bug
in tracker for blithely consuming all instances, or a kernel bug for
inotify being crap in the first place.
Since you are working on a kernel patch, I've opened a task for that and
assigned it to you
** Also affects:
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: Jamie (jamiemcc) = Jamie McCracken (jamiemcc-blueyonder)
--
tracker doesn't leave any for the rest of the class
https://bugs.launchpad.net/bugs/158040
You received this bug notification because you are a member of Ubuntu
Bugs, which is
12 matches
Mail list logo
