Hi ,what i mean is that for example a small but critical file like a keepass database wont be updated due to the changes being too small, but nexrcloud/google drive compare the file on local device and the file on the server and even the smallest of changes will resault in an update ,doea Syncthing support this now? Or is it yet to come?
To be frank, I’m not sure what you mean exactly. Could you rephrase the question, possibly being more specific? Syncthing’s got no problem detecting file changes regardless of their “size”. Have you actually experienced issues with Syncthing being unable to detect changes in those files? If yes, a detailed explanation (with screenshots, logs, etc.) will be helpful to properly diagnose the issue.
Wel for example
The main problem is lack of live syncing for small files. Has it been implemented?
That has nothing to do with small files or small changes. Some databases are memory mapped, which from our perspective means that they change contents without any metadata (size, modification time, etc) indicating that they’ve changed. Those won’t be synced until the metadata changes, probably when the database is closed by the program using it.
So if you mean “can Syncthing detect changes by always comparing file contents when the metadata didn’t change”, then no.
2 Likes
As you mentione keepass: That’s a regular file on disk, it does get synced fine - source: Me, using it.
2 Likes
and me
1 Like
Yeah that’s the only scenerio I can think of either, as to why the file would not be detected as changed. Though, I wonder under what conditions would the file metadata not change? The mtime (date modified) should update at least, unless the user was playing with the system clock somehow.
You mentioned not knowing how to recreate the “malfunction” (or perhaps lack of function), but what leads you to mention one kilobyte as the definition of a small file? Was that simply the approximate size of the file you were working with? Or did you test this with many files of sizes up to and above one kilobyte?
Don’t beat a dead horse. It has already been established that the OP was based on a misunderstanding.
1 Like