Rob Malpass <li...@getiton.myzen.co.uk> wrote:
>Hi all
>
>
>
>This may or may not be of interest to rsync fans (and by the way many
>many
>thanks for all of your help the other week). Here's the situation..
>
>
>
>One of the files I want to backup is an rsync container. As it's a
>container, its' file size is always 100Gb exactly and (I've just
>checked)
>that its' date stamp remains the date I physically moved it from its'
>previous home to my new server - despite the fact the contents have
>changed
>daily since then. So if (as according to rsync's man page) the
>algorithm
>checks for a change in file size or date stamp - it will determine this
>file
>doesn't need attention. Anybody know of a way to bypass this and
>force it
>to copy the file every time?
>
>
>
>It's no great strife of course to just zap the file every time I do the
>backup (or even add a simple cp to the backup script that runs the job)
>but
>just wondered if anyone's come across this before and found a more
>"elegant"
>workaround.
>
>
>
>Cheers
>
>Rob
>
>
>
>------------------------------------------------------------------------
>
>--
>Please post to: Hampshire@mailman.lug.org.uk
>Web Interface: https://mailman.lug.org.uk/mailman/listinfo/hampshire
>LUG URL: http://www.hantslug.org.uk
>--------------------------------------------------------------
Can you 'touch' the file to change its timestamp? Otherwise I can't see a way
of doing it.
cheers, Chris
--
Chris Dennis
Fordingbridge, Hampshire
--
Please post to: Hampshire@mailman.lug.org.uk
Web Interface: https://mailman.lug.org.uk/mailman/listinfo/hampshire
LUG URL: http://www.hantslug.org.uk
--------------------------------------------------------------
