Hi
On 5.3 i have a situation where some boxes have been 3 or 4 seconds out
and restarting ntpd has fixed the issue.
What i dont understand is why the clocks did not drift to the correct
time when the config seems correct in that restarting ntp did correct
the time.
Is there something
Tom Brown wrote:
Hi
On 5.3 i have a situation where some boxes have been 3 or 4 seconds out
and restarting ntpd has fixed the issue.
What i dont understand is why the clocks did not drift to the correct
time when the config seems correct in that restarting ntp did correct
the time.
Is
Is the directory /var/lib/ntp present, and with write permissions for
the 'ntp' user? Does the drift file exist?
Does ntpd ever lock in? What do you see in 'ntpq -p' over time?
Are these heavily-loaded boxes, or boxes with wildly-varying loads?
$ ll /var/lib/ntp
total 4
-rw-r--r-- 1
Tom Brown t...@... writes:
Hi
On 5.3 i have a situation where some boxes have been 3 or 4 seconds out
and restarting ntpd has fixed the issue.
What i dont understand is why the clocks did not drift to the correct
time when the config seems correct in that restarting ntp did correct
4 matches
Mail list logo
