**** BEGIN LOGGING AT Fri May 29 02:59:59 2015 May 29 06:16:54 morning all May 29 07:41:35 good morning May 29 09:30:12 morning all May 29 17:28:00 I've been getting strange errors from bitbake dealing with adding watches: "No space left on device or exceeds fs.inotify.max_user_watches." I tried to manually create a new watch on a file and confirmed that I've reached the upper limit on inotify watches. I've modified fs.inotify.max_user_watches to be 65k (up from the default of 8k), but I'm still having this issue. Has anyone else run into this before? May 29 17:31:23 connor__: I haven't, but do you have an unusually large number of files within your metadata? May 29 17:37:13 (Forgive my ignorance, I'm new to OE) I don't think so. This just happened when I tried to (re)build the default core-image-sato image. May 29 17:40:45 hmm, ok May 29 17:41:20 there must be some strange interaction with your system and our use of inotify May 29 17:44:52 looking at the code I can't see a built-in way to determine which paths are being watched, so I suspect the only way would be to modify the code and add some instrumentation May 29 17:45:34 if you're familiar with python, the code is in bitbake/lib/bb/cooker.py (search for inotify) May 29 17:46:51 connor__: in any case, if you wouldn't mind, it would be great if you could file a bug at http://bugzilla.yoctoproject.org (under bitbake) May 29 17:58:19 hmm, it looks like it's failing on the first watch it tries to add (oe-core/build/conf), which makes me think some other process on my machine is hogging all of them(?) May 29 18:00:01 confirmed. closing Sublime Text allowed bitbake to build. Thanks for your help! May 29 18:04:06 connor__: aha, interesting... perhaps it's sublimetext that's being a bit overexuberant with its watches in that case - well, assuming you don't have 8000 files open in it :) **** ENDING LOGGING AT Sat May 30 02:59:59 2015