You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Notify version (or commit hash if building from git): 6.1.1
What you did (as detailed as you can)
I was watching in NonRecursive mode a directory containing a single file.
What you expected
I expected to get notifications on file changes.
What happened
No notifications were delivered.
I fixed the issue by setting RecursiveMode::Recursive, even if the folder just contain a simple file (no nested folders).
This only happens on FreeBSD... maybe a problem with kqueue?
The text was updated successfully, but these errors were encountered:
This is how kqueue works – it requires to open an FD for every watched file. Thus, I believe it's not the fault of this crate but rather a limitation of kqueue. For reference, see this paragraph in the README of Go's fsnotify:
kqueue requires opening a file descriptor for every file that's being watched; so if you're watching a directory with five files then that's six file descriptors. You will run in to your system's "max open files" limit faster on these platforms.
This explains why recursive is necessary, as all files in a directory need to be watched explicitly.
System details
What you did (as detailed as you can)
I was watching in
NonRecursive
mode a directory containing a single file.What you expected
I expected to get notifications on file changes.
What happened
No notifications were delivered.
I fixed the issue by setting
RecursiveMode::Recursive
, even if the folder just contain a simple file (no nested folders).This only happens on FreeBSD... maybe a problem with
kqueue
?The text was updated successfully, but these errors were encountered: