I had takana working fine for a while...now out of NOWHERE it won't save to the scratch directory, and therefor no updates are pushed to the browser (because theres no file to push)
A little research led me to this:
ENOSPC means error no space, some people said that means there is no space on disk to write too, but in this case it actually means theres no more watches available...it has to do with the kernel, if you use the following parameter inside sysctl to set it, there is no more ENOSPC fs watch errors, as the kernel will now do its thing like it should.
I had takana working fine for a while...now out of NOWHERE it won't save to the scratch directory, and therefor no updates are pushed to the browser (because theres no file to push)
A little research led me to this:
ENOSPC means error no space, some people said that means there is no space on disk to write too, but in this case it actually means theres no more watches available...it has to do with the kernel, if you use the following parameter inside sysctl to set it, there is no more ENOSPC fs watch errors, as the kernel will now do its thing like it should.
sysctl fs.inotify.max_user_watches=524288
sources: http://stackoverflow.com/questions/16748737/grunt-watch-error-waiting-fatal-error-watch-enospc https://groups.google.com/forum/#!topic/nodejs/LX7sz9f-fmY http://linux.die.net/man/2/inotify_add_watch https://wiki.archlinux.org/index.php/Sysctl
I understand if the repo owner doesn't respond to these issues, because they are really issues with how npm works not takana.