Re: [Duplicity-talk] Preventing access time modification?

[mike]

agreed - not to mention it would save some performance overhead.

however, isn't that something done at a lower-level than the language?
i would think the atime stuff is done on the filesystem level, which
could prove challenging to stop on the python level (but i could
totally be wrong)

On 6/12/07, Axel Beckert <address@hidden> wrote:

> And there's one big annoyance: Many classical unix text-mode MUAs
> recognize mailboxes with new, unread mail by comparing modification
> time with (read) access time. If the last one is older, there must be
> new unread mail in mailbox. But if duplicity runs in the nightly
> backup run, it changes the access time and therefore, the MUAs think,
> there's no new mail in that mailbox.