Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

no response about "watches limit" from inotify #187

Closed
gumieri opened this issue Feb 11, 2014 · 4 comments
Closed

no response about "watches limit" from inotify #187

gumieri opened this issue Feb 11, 2014 · 4 comments

Comments

@gumieri
Copy link

gumieri commented Feb 11, 2014

O.S.: Ubuntu 12.04.4 LTS

Monday the Guard stopped responding modifications of files, there was no sign of error / exception.
The only update has been Git for version 1.8.5.4, I suspected that the problem would be in inotify.

I solved the problem by increasing the "max_user_watches" with the command:

sudo sysctl fs.inotify.max_user_watches=16364

I do not know if anyone else has gone through this problem, but it was a bit costly find out what was happening.

@thibaudgg
Copy link
Member

Have you try to ignore unwatched files? .git folder is ignored by default: https://github.com/guard/listen/blob/master/lib/listen/silencer.rb#L6

@gumieri
Copy link
Author

gumieri commented Feb 11, 2014

I mentioned git because it was the only update on my environment and could have interfered with inotify, since I have not updated any gem project.

But the major complication was the Guard / Listen not given any feedback that he was unable to use inotify.

@thibaudgg
Copy link
Member

Ok I see, a PR to improve the feedback would be much appreciated. Thanks!

@e2
Copy link
Contributor

e2 commented May 14, 2014

This was fixed in:
4e245ce

(Celluloid caught the abort with the INOTIFY warning and ... didn't ... show ... anything...)

@e2 e2 closed this as completed May 14, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants