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
fat and ntfs file system timestamp resolutions are different namely 2s and 100ms. Thus when syncing with different file system although the file is not changed , dirsync updates the files again again.Suggestion:
epsilon value in _cmptimestamps function might be setup based on file system working on.
Maybe the most robust thing to do would be to set the timestamp of the origin file to the one of the target file when copying, after the copy if they differ regardless of the file systems? It may slow things a bit, though ...
Original report by Anonymous.
fat and ntfs file system timestamp resolutions are different namely 2s and 100ms. Thus when syncing with different file system although the file is not changed , dirsync updates the files again again.Suggestion:
epsilon value in _cmptimestamps function might be setup based on file system working on.
mtime_cmp = int((filest1.st_mtime - filest2.st_mtime) * 1000) > 0
The text was updated successfully, but these errors were encountered: