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
We're using the latest master which is 3.0.0 release with the addition of 48c49a1
We're only interested in move and delete events, specifically of files, but we'd like to watch for files inside subdirs as well, so we're defining it like this:
the approach seems to be to add the WDs when either a file is CREATEd or a directory fires its own event (create, modify, whatever)
so in order to achieve what we're looking for, we need to add DirCreatedEvent in addition to the two events that we're after.
which means more CPU and RAM, slower performance and noisy debug logs
how can this be improved?
I would expect that when selecting recursive=True internally, we will implicitly add IN_ISDIR without IN_CREATE to reduce the noise of all file creations, and still identify new directories created to add watches
The text was updated successfully, but these errors were encountered:
We're using the latest master which is 3.0.0 release with the addition of 48c49a1
We're only interested in move and delete events, specifically of files, but we'd like to watch for files inside subdirs as well, so we're defining it like this:
I understand that inotify does not support recursive scanning,
and based on the implementation here:
the approach seems to be to add the WDs when either a file is CREATEd or a directory fires its own event (create, modify, whatever)
so in order to achieve what we're looking for, we need to add
DirCreatedEvent
in addition to the two events that we're after.which means more CPU and RAM, slower performance and noisy debug logs
how can this be improved?
I would expect that when selecting
recursive=True
internally, we will implicitly addIN_ISDIR
withoutIN_CREATE
to reduce the noise of all file creations, and still identify new directories created to add watchesThe text was updated successfully, but these errors were encountered: