duplicity-team team mailing list archive

[edso <question668404@xxxxxxxxxxxxxxxxxxxxx>]

Question #668404 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/668404

    Status: Open => Answered

edso proposed the following answer:
On 30.04.2018 11:22, Tim wrote:
> Question #668404 on Duplicity changed:
> https://answers.launchpad.net/duplicity/+question/668404
> 
>     Status: Answered => Open
> 
> Tim is still having a problem:
> Yes, atime is a filesystem feature.  But it is possible to
> programatically read and store the original atime, then read the file,
> then restore the original atime — using utimes() — such that atime
> effectively does not change.  I am wondering if Duplicity 'preserves'
> the original atime in such a manner.
> 

given the age of the original source i'd guess not. if you really want
to know you can easily check the sources yourself, or easier create a
test dataset. back it up and check atimes before and after.

@Ken: do you know it off the top of your head?

..ede/duply.net

-- 
You received this question notification because your team duplicity-team
is an answer contact for Duplicity.