On 29 October 2012 08:16, Tristan Seligmann <mithra...@mithrandi.net> wrote:
> If an offset of 128ms occurs at any time other than initial ntpd > startup (which will presumably occur at system startup), that means > you've either experienced a significant period of time without > connectivity to time servers[1], you have a hardware / kernel issue > that should be resolved, or some other software on the system is > messing with the clock. Aside from network issues, the other > possibilities are all serious issues that should be corrected, not > tolerated as a normal situation. > In my experience this sort of time drift happens quite frequently on virtual machines.
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
