Hi,
>
> One option would be:
> "-c, --checksum"
>
> But that would likely be extremely slow on a file of that size.
A checksum is designed to be quick to calculate so it should not
be that bad, however if the file is huge and almost certain to
have changed then it's pointless waste of CPU on both server and
client.
> If it were me, I would just "touch" the file after every rsync, so the
> next rsync would see it as changed.
You can always use the:
-I or --ignore-times
don't skip files that match size and time
Which would be the same as touch.
Why not test them both out and see what works best?
One other thing to rember is that if it's a file full of holes -
as containers tend to be, make sure you copy it maintaining them.
I think the sparse option is -S
--
Adam Trickett
Overton, HANTS, UK
Reality leaves a lot to the imagination.
-- John Lennon
--
Please post to: Hampshire@???
Web Interface:
https://mailman.lug.org.uk/mailman/listinfo/hampshire
LUG URL:
http://www.hantslug.org.uk
--------------------------------------------------------------
