On changeNotify refresh directory instead of invalidate

So currently, when running rclone mount changeNotify invalidates the directory on the vfs cache.
Then the directory needs to get refreshed on the vfs cache by either manually accessing the directory through the mount or through a scheduled rc vfs/refresh call.

Now my question is why not refresh the directory as soon as we get the notification about the change?

What if you don't use the directory? Why make an API call and refresh something if it isn't used. If there is a change and polling picks it up, the next use would grab it.

Also, if you had a mount changing a lot, you'd get stuck in a cycle of just constantly refreshing.

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.