Re: [Duplicity-talk] changed files not being backed up

[Kenneth Loafman]

Change time, ctime, is for any modification of the file, i.e. content or metadata.  Modification time, mtime, only registers the change of content on the inode.  So, if we go to ctime, the file will be backed up if any metadata changes, which is probably the way it should be.

However, I'm willing to bet some will argue the current check is correct.  I seem to remember this discussion happening before.

...Ken

On Fri, Dec 23, 2011 at 8:24 AM, Roy Badami <address@hidden> wrote:

On 23/12/2011 12:21, Wolfgang Rohdewald wrote:

Am Freitag, 23. Dezember 2011, 12:57:52 schrieb Georg Lutz:

But strong checksumming is not necessary here. It would be enough to
compare ctime instead of mtime.

better compare both

I don't think there's any need to compare both - the ctime should be updated by all operations that modify the inode in any way, so it shouldn't be possible to have the mtime change without the ctime also chaning.

--
Roy Badami
Roboreus Ltd
Third Floor
The Place
175 High Holborn
London WC1V 7AA

_______________________________________________
Duplicity-talk mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/duplicity-talk