Difference between revisions for inotify





Revision 1 as of 08/20/2019 23:00 ▼
3 08/20/2019 23:22 EvaggelosBalaskas 2 08/20/2019 23:05 EvaggelosBalaskas 1 08/20/2019 23:00 EvaggelosBalaskas

(1.1 KiB)
EvaggelosBalaskas
 Next edit →
Revision 4 as of 08/21/2019 23:10 ▼
5 08/21/2019 23:13 EvaggelosBalaskas 4 08/21/2019 23:10 EvaggelosBalaskas 3 08/20/2019 23:22 EvaggelosBalaskas 2 08/20/2019 23:05 EvaggelosBalaskas

(1.2 KiB) +146
EvaggelosBalaskas

Version1 Version2 Differences
2 2
3 3 The inotify(7) subsystem has three important tunings that impact watchman.
4 4
5     * /proc/sys/fs/inotify/max_user_instances impacts how many different root dirs you can watch.
6     * /proc/sys/fs/inotify/max_user_watches impacts how many dirs you can watch across all watched roots.
7     * /proc/sys/fs/inotify/max_queued_events impacts how likely it is that your system will experience a notification overflow.
  5   * !!/proc/sys/fs/inotify/max_user_instances!! impacts how many different root dirs you can watch.
  6   * !!/proc/sys/fs/inotify/max_user_watches!! impacts how many dirs you can watch across all watched roots.
  7   * !!/proc/sys/fs/inotify/max_queued_events!! impacts how likely it is that your system will experience a notification overflow.
8 8
9 9 You obviously need to ensure that max_user_instances and max_user_watches are set so that the system is capable of keeping track of your files.
10 10
… … …
17 17 ((https://en.wikipedia.org/wiki/Inotify Inotify - Wikipedia))
18 18
19 19 ((https://linux.die.net/man/7/inotify Inotify - Man Page))
  20  
  21 ((https://github.com/torvalds/linux/tree/master/fs/notify/inotify inotify - kernel))  
  22  
  23 %%  
  24 inotifywait -mr -e close_write /storage/  
  25 %%