Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
DST disrupting rsync twice a year
I'm facing rsync full syncs every once upon a time, I think it's because DST, notice an hour of difference:
$ ls -l tier2/VIDEO-2020-06-17-15-10-27.mp4 /Volumes/KINSTON2/dat/laptop_kinstones/tier2/VIDEO-2020-06-17-15-10-27.mp4
-rwxrwxrwx 1 ****** staff 3992777 Jun 18 09:57 /Volumes/KINSTON2/dat/laptop_kinstones/tier2/VIDEO-2020-06-17-15-10-27.mp4
-rw-r--r--@ 1 ****** staff 3992777 Jun 18 08:57 tier2/VIDEO-2020-06-17-15-10-27.mp4
Used options are:
$ rsync \
--itemize-changes \ # just learned about this, helped me diagnostic
--progress \ # most often not
--recursive \
--no-owner --no-group \ # because backing up towards MSDOS persistence
--no-perms \ # same as above?
--times \
--delete \ # because backing up the left side
--modify-window=3 \ # because backing up towards MSDOS persistence
--verbose \ # because craving for feedback
--dry-run \ # unless not quite
tier2/ \ # src
/Volumes/KINSTON2/dat/laptop_kinstones/tier2/ # dst
thx in advance (✿◠‿◠)
Notice: this enters here as a verbatim copy (excluding this notice) of post 278965 now residing closed and deleted in the Q&A category of the Meta site.
1 answer
Solved this æons ago actually...
[Assumes Bash shell].
If the DST difference is for instance an hour (or 60 minutes, or 3600 seconds), change:
--modify-window=3
To:
--modify-window=$((3 + 60 * 60))
This might save the day, with the only undesirable consequence that you now need to wait for an hour between syncs, which mmmight be possssible for many scenarios... like for instance my scenario. (✿◠‿◠)
0 comment threads
1 comment thread