Fork of https://github.com/fsnotify/fsnotify
Contains patches for Tilt Dev.
- [macOS] Fix for panic when debugging (fsnotify/fsnotify#212)
- [Windows] Recursive watch support
- [Windows] Customizable buffer size
- [Windows] File attribute changes are ignored
- No
Chmodoperations will be detected or returned on Windows because the underlying Windows API does not support distinguishing these fromWriteoperations - Some software (likely AV/security) can cause excessive attribute changes resulting in many spurious write events for otherwise unchanged files
- No
fsnotify utilizes golang.org/x/sys rather than syscall from the standard library.
Cross platform: Windows, Linux, BSD and macOS.
| Adapter | OS | Status |
|---|---|---|
| inotify | Linux 2.6.27 or later, Android* | Supported |
| kqueue | BSD, macOS, iOS* | Supported |
| ReadDirectoryChangesW | Windows | Supported |
| FSEvents | macOS | Planned |
| FEN | Solaris 11 | In Progress |
| fanotify | Linux 2.6.37+ | Maybe |
| USN Journals | Windows | Maybe |
| Polling | All | Maybe |
* Android and iOS are untested.
Please see the documentation and consult the FAQ for usage information.
fsnotify is a fork of howeyc/fsnotify with a new API as of v1.0. The API is based on this design document.
All releases are tagged based on Semantic Versioning.
package main
import (
"log""github.com/fsnotify/fsnotify"
)
funcmain() {
watcher, err:=fsnotify.NewWatcher()
iferr!=nil {
log.Fatal(err)
}
deferwatcher.Close()
done:=make(chanbool)
gofunc() {
for {
select {
caseevent, ok:=<-watcher.Events:
if!ok {
return
}
log.Println("event:", event)
ifevent.Op&fsnotify.Write==fsnotify.Write {
log.Println("modified file:", event.Name)
}
caseerr, ok:=<-watcher.Errors:
if!ok {
return
}
log.Println("error:", err)
}
}
}()
err=watcher.Add("/tmp/foo")
iferr!=nil {
log.Fatal(err)
}
<-done
}Please refer to CONTRIBUTING before opening an issue or pull request.
When a file is moved to another directory is it still being watched?
No (it shouldn't be, unless you are watching where it was moved to).
When I watch a directory, are all subdirectories watched as well?
No, you must add watches for any directory you want to watch (a recursive watcher is on the roadmap #18).
Do I have to watch the Error and Event channels in a separate goroutine?
As of now, yes. Looking into making this single-thread friendly (see howeyc #7)
Why am I receiving multiple events for the same file on OS X?
Spotlight indexing on OS X can result in multiple events (see howeyc #62). A temporary workaround is to add your folder(s) to the Spotlight Privacy settings until we have a native FSEvents implementation (see #11).
How many files can be watched at once?
There are OS-specific limits as to how many watches can be created:
- Linux: /proc/sys/fs/inotify/max_user_watches contains the limit, reaching this limit results in a "no space left on device" error.
- BSD / OSX: sysctl variables "kern.maxfiles" and "kern.maxfilesperproc", reaching these limits results in a "too many open files" error.
Why don't notifications work with NFS filesystems or filesystem in userspace (FUSE)?
fsnotify requires support from underlying OS to work. The current NFS protocol does not provide network level support for file notifications.