Nathan Youngman

@phred I've been doing some experimentation with kqueue. When using a `nil` timeout to block until there is an event, CPU usage is reduced to 0% while idle.

@dennisconrad Thanks for the report. Unfortunately I don't have a Red Hat VM setup yet. Go 1.3 will include os/fsnotify in standard library. We are in the process of moving...

@dennisconrad Do you still see this issue under RHEL? What about CentOS?

@michael-martin-al I'm not sure if this issue still exists? I'm curious if running the fsnotify test suite on CentOS results in failures? - If the tests fail, we should consider...

@michael-martin-al If this is still an issue with the latest code (`go get -u github.com/howeyc/fsnotify`) would you mind opening the issue over at https://code.google.com/p/go/issues/list?q=fsnotify (for go.exp/fsnotify)? We are currently transitioning...

We currently use kqueue on OS X which is limited to 10,240 open file descriptors (number of files watched). I found this article to increase the limit but I haven't...

File descriptors are used for other things too, even if you're only using a few hundred. I'm not aware of any other limits besides # of files. One thing you...

> "The default per-process descriptor limit on current versions of OS X is extremely low (256!). " From the [Watchman README](https://github.com/facebook/watchman#max-os-file-descriptor-limits)

@pifantastic Based on the discussions around inclusion of os/fsnotify in standard library, I suspect a separate polling package would be best, but you can bring it up on the golang-dev...

:+1: Having a cache breaker in production filenames is a nice feature of webassets.