21 Jan
2010
21 Jan
'10
4:42 p.m.
Alastair Sherringham wrote:
2010/1/21 Nigel Rantor <wiggly(a)wiggly.org
<mailto:wiggly@wiggly.org>>
I'm not sure about Lenny/xen specific issues but the fact that machines
coming up can have deltas large enough to stop ntpd from adjusting the
clock is not uncommon, and normally you find people run ntpdate in
whatever rc file starts up ntpd so that ntp is able to adjust the time
from then on.
Thanks Nigel. Note - ntpdate is happy to adjust this - but dovecot
thinks this is bad and kills itself to prevent problems
(http://wiki.dovecot.org/TimeMovedBackwards).
Yeah, I understand, as long as the ntp rc script starts up before
dovecot then by the time dovecot is up and running things should be
fine. Lots of things get unhappy if the time apparently changes
underneath them.
This large time delta on boot is a big change from
Debian Etch.
Did you have ntpd running on that machine?
Either way, I'd still recommend ntpdate/ntp. For example, it also takes
acre of situations where, for example, a desktop machine's battery has
died and it is no longer keeping time when powered down.
I am not running NTP - just ntpdate (cron - set clock
once a day). Maybe
I shouldn't.
Ah, yes, that might do it. I would suggest you run ntpdate once only on
bootup to get the time correct so that ntp can then keep your clock from
slewing too far out of alignment from then on.
n