Re: 30 Minutes (system time/ntpdate/dovecot)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, Jun 07, 2009 at 05:07:08PM +0300, David Baron wrote:
> Has been happening quite a bit lately:
>
> Problem with ntpdate. If and when it finally works, get a change of 10,800
> seconds ... that is 30 minutes.
>
> The dovecot IMAPd server is unreadable. Restarting it yields a complaint about
> 10,800 seconds of time, killing itself now! Restarting it again works OK.
>
> What's happening? Bug? Fix?
I've had nothing but great results with chrony. Aside from an issue of
chrony falling back to 127.127.1.1 when it cannot connect to a ntp server..
Which happens often with my laptop as I move around during the day.. I
fixed that by restarting the service hourly with cron. I'm never more
than a half second off across boots and stupid accurate while connected.
System time : 0.000000 seconds fast of NTP time
http://www.linuxjournal.com/article/5657
- --
Daryl Styrk
Naples FL, USA
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkor1eYACgkQ6baBhW8CzrgmpQCfWe4RNDLP004TwGkOVmOVNzn7
esAAnAjmV5PTMVGdK/pDz5mWPpHIZtQm
=bbnl
-----END PGP SIGNATURE-----
Reply to: