-
Notifications
You must be signed in to change notification settings - Fork 668
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use MD5 sum to confirm file has changed. #110
Labels
Comments
waiting for owncloud/core#523 to be resolved. |
This was referenced Sep 30, 2013
Please track #2542 |
Re-opening, this is about different issues. |
duplicate: #3235 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
** Reopened issue from owncloud/core#523 ***
[See forum posting @ http://forum.owncloud.org/viewtopic.php?f=3&t=5612]
I have a home OC server (4.5.2) up and running on a Linux box.
I took a copy of my parents' photos (13Gig of data) on to a USB disk, took the disk home and then copied the photos (using my local network) on the OC server.
I now setup a sync between the photos directory on my parents' PC (client 1.1.1) and the copy on the OC server at my house.
But the client on my parent's PC is a bit stupid and clearly doesn't check the actual file contents, and so starts to copy all the photos back across to the server.
This is a completely pointless operation.
Surely an md5sum (or similar hash calculation) should be performed to determine if a file copy is required. This is how rsync works under Linux.
I now understand that you only check the modification timestamps, but I would have thought a behaviour like the following would be possible:-
(a) if timestamp has not changed, do nothing
(b) if timestamp has changed, perform an md5sum to confirm the contents have change
(c) if the contents have changed, copy the file data
(d) if the contents have not changed, but the timestmpa has, then just sync the timestamps.
Or at least make this an option !?!
The text was updated successfully, but these errors were encountered: