meonkeys (3) [Avatar] Offline
#1
From "RINSE AND REPEAT – WATCHING FOR CHANGES":

When Meteor can use either kqueue or inotify it falls back to a 5000ms interval...


I believe "can" should be "cannot".
stephan.hochhaus (92) [Avatar] Offline
#2
Hey meonkeys,

funny thing, but this is actually not a typo smilie

See this link

By default, meteor uses both inotify/kqueue and stat polling, with a polling interval of 5 seconds; if it detects that inotify/kqueue isn't working, it uses a polling interval of 0.5 seconds.


Would you suggest we change the wording so that it is clearer?
meonkeys (3) [Avatar] Offline
#3
Ah! Thanks.

That sounds like understandably complex logic. Error handling is tricky ("if meteor was unable to automatically detect that inotify/kqueue didn't work, you may have to wait up to 5 seconds for stat polling to notice file changes").