Bruce Cran wrote:
Volker Jahns wrote:
On Thu, May 15, 2008 at 09:53:02PM +0200, Volker Jahns wrote:
On Thu, May 15, 2008 at 12:18:57PM -0700, Chuck Swiger wrote:
On May 15, 2008, at 11:57 AM, Volker Jahns wrote:
FreeBSD 6.2 running on X86 hardware (FSC) shows a remarkable time
drift
Volker Jahns wrote:
Bruce Cran wrote:
Volker Jahns wrote:
On Thu, May 15, 2008 at 09:53:02PM +0200, Volker Jahns wrote:
On Thu, May 15, 2008 at 12:18:57PM -0700, Chuck Swiger wrote:
On May 15, 2008, at 11:57 AM, Volker Jahns wrote:
FreeBSD 6.2 running on X86 hardware (FSC) shows a remarkable
On May 15, 2008, at 11:57 AM, Volker Jahns wrote:
FreeBSD 6.2 running on X86 hardware (FSC) shows a remarkable time
drift
running ntpdate every half hour shows that the system looses about
10-14 sec each time.
15 May 10:06:48 ntpdate[7200]: step time server 192.53.103.108
offset
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Volker Jahns
Sent: Thursday, May 15, 2008 2:58 PM
To: freebsd-questions@freebsd.org
Cc: [EMAIL PROTECTED]
Subject: time drift
FreeBSD 6.2 running on X86 hardware (FSC) shows a remarkable time drift
running
On Thu, May 15, 2008 at 12:18:57PM -0700, Chuck Swiger wrote:
On May 15, 2008, at 11:57 AM, Volker Jahns wrote:
FreeBSD 6.2 running on X86 hardware (FSC) shows a remarkable time
drift
running ntpdate every half hour shows that the system looses about
10-14 sec each time.
15 May
On Thu, May 15, 2008 at 09:53:02PM +0200, Volker Jahns wrote:
On Thu, May 15, 2008 at 12:18:57PM -0700, Chuck Swiger wrote:
On May 15, 2008, at 11:57 AM, Volker Jahns wrote:
FreeBSD 6.2 running on X86 hardware (FSC) shows a remarkable time
drift
running ntpdate every half hour shows
On Thu, May 15, 2008 at 08:57:59PM +0200, Volker Jahns wrote:
FreeBSD 6.2 running on X86 hardware (FSC) shows a remarkable time
drift
running ntpdate every half hour shows that the system looses about 10-14 sec
each time.
15 May 10:06:48 ntpdate[7200]: step time server 192.53.103.108
David Kelly wrote:
Its PC commodity-grade. Not all that unusual even for stuff sold
claiming to be a server. This is in no small part why ntpd exists.
nptd calculates a correction coefficient and (under FreeBSD) stores it
in /var/db/ntpd.drift for use on next start so as to more quickly
Volker Jahns wrote:
On Thu, May 15, 2008 at 09:53:02PM +0200, Volker Jahns wrote:
On Thu, May 15, 2008 at 12:18:57PM -0700, Chuck Swiger wrote:
On May 15, 2008, at 11:57 AM, Volker Jahns wrote:
FreeBSD 6.2 running on X86 hardware (FSC) shows a remarkable time
drift
running ntpdate every
On May 15, 2008, at 2:16 PM, Christopher Cowart wrote:
We run a large number of FreeBSD servers under vmware. We've seen ntpd
silently die, because the drift becomes insane. What do others do in
this situation? (We've resorted to croning ntpdate for VMs.)
You run ntpd in the parent OS, rather
On Thu, 15 May 2008 at 14:16 -0700, [EMAIL PROTECTED] confabulated:
David Kelly wrote:
Its PC commodity-grade. Not all that unusual even for stuff sold
claiming to be a server. This is in no small part why ntpd exists.
nptd calculates a correction coefficient and (under FreeBSD) stores it
in
On May 15, 2008, at 12:53 PM, Volker Jahns wrote:
While you should run ntpdate -b at system boot, running ntpdate
periodically via cron is not the right thing to do-- you should run
ntpd instead, and that will figure out the intrinsic correction your
chosen system clock needs to keep better time
On Thu, 15 May 2008, Christopher Cowart wrote:
David Kelly wrote:
Its PC commodity-grade. Not all that unusual even for stuff sold
claiming to be a server. This is in no small part why ntpd exists.
nptd calculates a correction coefficient and (under FreeBSD) stores it
in /var/db/ntpd.drift
FreeBSD 6.2 running on X86 hardware (FSC) shows a remarkable time
drift
running ntpdate every half hour shows that the system looses about
10-14 sec each time.
15 May 10:06:48 ntpdate[7200]: step time ... offset -13.799602 sec
15 May 10:36:48 ntpdate[7515]: step time ... offset -12.813941
14 matches
Mail list logo
