Re: [Q] What might cause modification dates to shift later by an hour?

["Stephen Samuel (gmail)" <darkonc gmail com>]

One easy workaround would be to, when you start the backup program, to set it to a timezone that does not have  daylight savings time shifts.  (eg: " TZ=MST  run_my_backup"  )

This can be done on a per-process (or per-user) basis by setting the TZ environment  variable before 
starting the process (or in a user's .*profile file)

On Fri, Jun 26, 2009 at 3:00 PM, Maurice Volaski <mvolaski aecom yu edu> wrote:

Time zones are the culprit -- Specifically DST shifts.
If you check the absolute time stamp (which is GMT), it hasn't changed...
but the distance between you and GMT changed by one hour when the DST change kicked in.
Nothing has gone wrong, unless your backup software works internally with TZ shifted date stamps, in which
case it might get confused twice per yer.

Thanks for you answer. It looks like a bug in the backup software.

-- 
Stephen Samuel http://www.bcgreen.com  Software, like love, 
778-861-7641                              grows when you give it away