On Wed, 28 Nov 2012, Peter Ross <Peter.Ross@bogen.in-berlin.de> wrote:
On Tue, 27 Nov 2012, Russell Coker wrote:
But I prefer to just start it [ntpd] and let it do it's thing. If the difference is less than 20 minutes then it can manage it by itself.
Is your ntpd server inside a virtual machine?
No. Just a plain old P3 desktop system that's been running for years as a router.
In "virtualland" time is a problem. In short, there is only one timer in hardware, and the virtual machine may lose ticks if machines are busy with something else.
If "ntp time" and "system time" differ too much, ntpd stops synchronizing, and the gap widens.
That's about 20 minutes from memory, you need some severe problems to get to that stage. For my virtual servers I generally find that it's a few seconds of inaccuracy per day and I run ntpdate from a daily cron job to fix it. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/