On Wed, Jul 01, 2015 at 02:12:48PM +0000, [email protected] wrote:
> Interestingly enough, logging reports 1 big jump on my boxes about 1.5
Nah, that's not a jump. The message means: starting slowing
down/speeding up the clock to compensate. It takes a while for the
adjustment to be done. Once the clock gets closer to the time computed
from the references, the needed adjustement gets smaller.
-Otto
> hours after midnight. It's curious that there's only a report of a ~1s
> jump, then skew correction. Times are in UTC. I'm using constraints
> from google and pool.ntp.org as the server on 5.7/amd64.
>
>
> Jul 1 01:36:01 x ntpd[2021]: adjusting local clock by -0.995120s
> Jul 1 07:52:07 x ntpd[2021]: adjusting clock frequency by -30.002480 to
> -35.130664ppm
> Jul 1 09:35:39 x ntpd[2021]: adjusting local clock by 0.047839s
> Jul 1 10:04:27 x ntpd[2021]: adjusting local clock by 0.189961s
> Jul 1 10:57:29 x ntpd[2021]: adjusting local clock by 0.042814s
> Jul 1 11:02:15 x ntpd[2021]: adjusting local clock by 0.051244s
> Jul 1 11:06:29 x ntpd[2021]: adjusting clock frequency by 42.865357 to
> 7.734693ppm
> Jul 1 12:58:05 x ntpd[2021]: adjusting clock frequency by -12.782874 to
> -5.048181ppm
