no hash comparison when filename is the same
Asked by
Thomas Meyssonnier
Using Csync on two (almost) identical trees, I was surprised to find out it was pushing every single file.
In fact the files are the same, but the modification date is different because at some point, one of the trees went through a recursive chmod for system reasons.
I find myself with 48h of transfer (as I can evaluate) when almost none of the files should have been transfered if csync had checked the file hash before pushing. The only point in this is to get the same modification date, which is beside the point in that case.
Maybe csync should check the hash, even for files with the same path and different times. Sometimes it reflects a change not in the file itself.
Question information
- Language:
- English Edit question
- Status:
- Expired
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
To post a message you must log in.