Is the clock almost in sync? - if its too far out ntp will silently fail
to sync (by design - large scale time steps can be destructive for
heavily active databases for instance)
Check out the -g option to ntpd in 'man ntpd'
or 'tinker panic 0' in ntp.conf
Also, has ntp.conf specified a writable frift file in a directory that
ntp can be VERY complex when it doesnt "just work"
On Mon, 2011-01-03 at 19:31 -0600, Dale wrote:
> I been watching my clock here for a while. On my old rig, ntp kept the
> clock set very, very well. This rig seems to have issues. I tried the
> stable version of ntp and it just seems to keep resetting the time but
> not adjusting the drift file at all. I even adjusted manually once and
> my entry was better than the one it made.
> I then decided to try the latest unstable ntp to see if maybe it would
> work better. I emerged ntp, renamed the drift file and started the
> service. That was several hours ago and it has yet to even create the
> drift file. It also puts nothing in the log file except that it started
> and is using ports and the normal stuff. No syncing or anything like
> the older version.
> Also, I copied the ntp.conf file over from the old rig. I would think
> they would work pretty much the same. Same program, same config and
> hopefully same results.
> First version tried: net-misc/ntp-4.2.4_p7-r1
> Current unstable version: net-misc/ntp-4.2.6_p2-r1
> When I looked at the ntp website, it said it should sync much faster
> than the old one. Basically it is minutes instead of hours. So far
> this is not the case.
> Anybody else ran into this? Am I missing something that is different on
> a 64 bit rig?
> :-) :-)
William Kenworthy <email@example.com>
Home in Perth!