Whether or not fsnotify implements polling support itself, some thought should be given into how polling could work as an alternative to native OS events.
GoConvey uses polling exclusively to avoid the "too many files" error #8.
"we walk the file system every quarter second and use the sum of the last mod time stamp and size of each go file as a quick comparison. Along the way we make note of new and deleted packages, all the while skipping 'ignored' packages. It's actually quite speedy." - @mdwhatcott, Gopher Slack
If you use an approach like what I've done in GoConvey, make sure to count empty directories as well... - @mdwhatcott
https://github.com/smartystreets/goconvey/blob/master/web/server/watcher/scanner.go
@pifantastic reports that node's gaze (https://github.com/shama/gaze#errors) library detects EMFILE errors and falls back to polling.
Polling could be opt-in for network file systems (NFS), Vagrant or Plan 9 -- where OS events don't work or are unavailable.
Whether or not fsnotify implements polling support itself, some thought should be given into how polling could work as an alternative to native OS events.
GoConvey uses polling exclusively to avoid the "too many files" error #8.
https://github.com/smartystreets/goconvey/blob/master/web/server/watcher/scanner.go
@pifantastic reports that node's gaze (https://github.com/shama/gaze#errors) library detects
EMFILEerrors and falls back to polling.Polling could be opt-in for network file systems (NFS), Vagrant or Plan 9 -- where OS events don't work or are unavailable.