Just curious if using --track-renames means --check-first is implied, the documentation doesn't say. It seems like checking all the files first would be ideal so that an unnecessary transfer isn't started before renames are fully resolved.
I guess a redacted example from my logs explain better than a 1000 words:
INFO somefile1: Copied (replaced existing)
INFO somefile5: Copied (replaced existing)
INFO ... Making map for --track-renames
INFO ... Finished making map for --track-renames
INFO somefile7: Copied (new)
INFO somefile8: Copied (new)
INFO somefile2: Deleted
INFO somefile3: Deleted
So existing files are replaced while building the info to track renames, when the map is finished then new files are uploaded and finally the deletes are performed - unless additional flags are modifying default behavior. That is --check-first would also delay the upload of modified files.
1 Like
Forgot the important part, here is an example with tracked renames:
INFO somefile1: Copied (replaced existing)
INFO somefile5: Copied (replaced existing)
INFO ... Making map for --track-renames
INFO ... Finished making map for --track-renames
INFO somefile4: Moved (server-side) to: somefile4newname
INFO somefile6: Moved (server-side) to: some/other/folder/somefile6
INFO somefile7: Copied (new)
INFO somefile8: Copied (new)
INFO somefile2: Deleted
INFO somefile3: Deleted
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.