[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Duplicity-talk] Failures w/ S3 backend
From: |
Peter Schuller |
Subject: |
Re: [Duplicity-talk] Failures w/ S3 backend |
Date: |
Thu, 19 Mar 2009 20:36:20 +0100 |
User-agent: |
Mutt/1.5.19 (2009-01-05) |
> Glad you found it. Looks like it may be a boto issue.
IIRC the error message indicated that the S3 server actually failed
the request due to the date being wrong according to the server. I
suspect boto is simply sending the request in such a way that the date
is included, thus allowing the S3 service to fail the request when
detecting the problem.
This could be wrong of course, just pointing out that it's not
necessarily a bug in boto even if triggered by boto doing things
differently.
> I use ntp daemon for setting time. Lots of experience with funny
> problems cause by time drift, especially when using tools like 'make'.
Have you gotten ntp to react to suspend/resume and do some kind of
insta-synch? Normally ntpd does not like the clock being significantly
drifted and won't make a discontiguous jump until significant time has
passed.
--
/ Peter Schuller
PGP userID: 0xE9758B7D or 'Peter Schuller <address@hidden>'
Key retrieval: Send an E-Mail to address@hidden
E-Mail: address@hidden Web: http://www.scode.org
pgpiXWtLuokbC.pgp
Description: PGP signature
Re: [Duplicity-talk] Failures w/ S3 backend, Maurizio Vitale, 2009/03/19