Date: Sun, 21 Feb 2010 08:20:19 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: freebsd-stable@freebsd.org Subject: Re: ntpd struggling to keep up - how to fix? Message-ID: <4B80ECC3.1040200@infracaninophile.co.uk> In-Reply-To: <20100220234234.GB36973@icarus.home.lan> References: <20100212131117.GA51905@icarus.home.lan> <20100212174452.2140cd72.torfinn.ingolfsen@broadpark.no> <20100217194927.e3ec60ae.torfinn.ingolfsen@broadpark.no> <20100217200322.da66c9f8.torfinn.ingolfsen@broadpark.no> <20100218205458.GA78560@server.vk2pj.dyndns.org> <20100218231223.ec6b9fa8.torfinn.ingolfsen@broadpark.no> <20100219003844.acdaa866.torfinn.ingolfsen@broadpark.no> <20100220015351.GB81639@server.vk2pj.dyndns.org> <20100220223201.178e67dd.torfinn.ingolfsen@broadpark.no> <20100220225521.18586aaf.torfinn.ingolfsen@broadpark.no> <20100220234234.GB36973@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 20/02/2010 23:42, Jeremy Chadwick wrote:
> For sake of example -- look at ntpq's "delay" column for each peer, and
> then look at the same column but for ntpdc. You'll see that for ntpdc
> they're divided by 1000 (presumably kern.hz rate):
No -- those are just times measured in milliseconds (for ntpq) or
seconds (for ntpdc). kern.hz doesn't come into it.
Cheers,
Matthew
- --
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkuA7MMACgkQ8Mjk52CukIymTACfV62sN6DC8TQjnxhqS7w5r89l
m8MAn3vxDX8w2LpfA7ik67KXrhS2LY6G
=eRg0
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B80ECC3.1040200>