| commit | ceba4ef83ad7912d1ccf0b59e1ed8a13176f23b3 | [log] [tgz] |
|---|---|---|
| author | NitroCao <17915615+NitroCao@users.noreply.github.com> | Thu Apr 21 14:46:51 2022 +0800 |
| committer | GitHub <noreply@github.com> | Thu Apr 21 15:46:51 2022 +0900 |
| tree | 09af9b29a3a60b30099e20695e06f40626898fc9 | |
| parent | 712fe1d802d8c20c95e843adac4d8b11c1d636d1 [diff] |
Add a feature to return the directories and files that are being monitored (#374) * Add a feature to return the directories and files that are being monitored * add WatchList() method for bsd and windows platforms * preallocate space for the array to be returned
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"
)
func main() {
watcher, err := fsnotify.NewWatcher()
if err != nil {
log.Fatal(err)
}
defer watcher.Close()
done := make(chan bool)
go func() {
for {
select {
case event, ok := <-watcher.Events:
if !ok {
return
}
log.Println("event:", event)
if event.Op&fsnotify.Write == fsnotify.Write {
log.Println("modified file:", event.Name)
}
case err, ok := <-watcher.Errors:
if !ok {
return
}
log.Println("error:", err)
}
}
}()
err = watcher.Add("/tmp/foo")
if err != 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:
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.