Fixes issue #70

Not exactly the best fix, but it'll do.
1 file changed
tree: 7d4151cd361116c944ce1f8308e6d2e073f62eca
  1. .gitignore
  2. AUTHORS
  3. CONTRIBUTING.md
  4. LICENSE
  5. README.md
  6. Vagrantfile
  7. example_test.go
  8. fsnotify.go
  9. fsnotify_bsd.go
  10. fsnotify_linux.go
  11. fsnotify_open_bsd.go
  12. fsnotify_open_darwin.go
  13. fsnotify_symlink_test.go
  14. fsnotify_test.go
  15. fsnotify_windows.go
README.md

File system notifications for Go

Build Status

GoDoc

Cross platform, works on:

  • Windows
  • Linux
  • BSD
  • OSX

Example:

package main

import (
	"log"

	"github.com/howeyc/fsnotify"
)

func main() {
	watcher, err := fsnotify.NewWatcher()
	if err != nil {
		log.Fatal(err)
	}

	done := make(chan bool)

	// Process events
	go func() {
		for {
			select {
			case ev := <-watcher.Event:
				log.Println("event:", ev)
			case err := <-watcher.Error:
				log.Println("error:", err)
			}
		}
	}()

	err = watcher.Watch("testDir")
	if err != nil {
		log.Fatal(err)
	}

	<-done

	/* ... do stuff ... */
	watcher.Close()
}

For each event:

  • Name
  • IsCreate()
  • IsDelete()
  • IsModify()
  • IsRename()

Notes:

  • When a file is renamed 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.
  • 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.
  • 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.