FSEventStreamStart error logs in the startup
Closed this issue · 2 comments
raine commented
In some directories I don't get these and it still works, the output is annoying though.
~/D/c/walldisplay git:connect-livereload ❯❯❯ livereloadx -p 35730 ./static ⏎ ✱ ◼
2014-03-03 22:07:10 - info: Config:
2014-03-03 22:07:10 - info: - mode: default
2014-03-03 22:07:10 - info: - port: 35730
2014-03-03 22:07:10 - info: - filter:
2014-03-03 22:07:10 - info: 1: exclude ".{git,svn}/"
2014-03-03 22:07:10 - info: 2: include "*/"
2014-03-03 22:07:10 - info: 3: include "*.{html,shtml,tmpl,xml,css,js,json,jpeg,jpg,gif,png,ico,cgi,php,py,pl,pm,rb}"
2014-03-03 22:07:10 - info: 4: exclude "*"
2014-03-03 22:07:10 - info: Waiting on port 35730...
2014-03-03 22:07:10 - info: Watching "/Users/rainevi/app/static"...
2014-03-03 22:07 node[31369] (CarbonCore.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2014-03-03 22:07 node[31369] (CarbonCore.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2014-03-03 22:07 node[31369] (CarbonCore.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2014-03-03 22:07 node[31369] (CarbonCore.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2014-03-03 22:07 node[31369] (CarbonCore.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2014-03-03 22:07 node[31369] (CarbonCore.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2014-03-03 22:07 node[31369] (CarbonCore.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
2014-03-03 22:07 node[31369] (CarbonCore.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-21)
raine commented
It seems that this occurs because of the huge number of files being watched.
Doesn't happen if I add --ignore node_modules/
👍
raine commented
I lied. You can't fix it with --ignore
Seems to be fixed in node 0.11v
gruntjs/grunt-contrib-watch#292