-
Notifications
You must be signed in to change notification settings - Fork 247
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
Number of inotify watches was reached #24
Comments
Thanks for reporting this. This is actually documented in the guard README file ("Advanced Linux system configuration"), but we will include it in the README of Listen too. |
What do you think about rescuing this error and inform the use about the command line to run? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Not really a issue, but I ran in a problem on Linux where I hit the max number of inotify watches.
Doing the following, seems to fixed the issue :
Here is the dump it generates when you hit the limit.
/usr/local/rvm/gems/ruby-1.9.2-p290/gems/listen-0.4.1/lib/listen/adapter.rb:132:in
ensure in works?': undefined method
stop' for nil:NilClass (NoMethodError)from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/listen-0.4.1/lib/listen/adapter.rb:132:in
works?' from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/listen-0.4.1/lib/listen/adapter.rb:102:in
block in usable_and_works?'from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/listen-0.4.1/lib/listen/adapter.rb:102:in
each' from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/listen-0.4.1/lib/listen/adapter.rb:102:in
all?'from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/listen-0.4.1/lib/listen/adapter.rb:102:in
usable_and_works?' from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/listen-0.4.1/lib/listen/adapter.rb:36:in
select_and_initialize'from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/listen-0.4.1/lib/listen/listener.rb:183:in
initialize_adapter' from /usr/local/rvm/gems/ruby-1.9.2-p290/gems/listen-0.4.1/lib/listen/listener.rb:44:in
block in start'The text was updated successfully, but these errors were encountered: