On Mon, Dec 29, 2025 at 05:37:02AM +0000, H. Hartzer wrote:
> Hi misc@,
>
> This may actually be a bug -- it's just so odd that I wanted to run it
> by here first.
>
> Running a syspatched 7.8 (amd64) on a Xeon E5-2650 v2.
>
> Clock is off, ntpd tries to correct it, but it never does.
>
> Here's an example:
>
> Dec 29 05:19:23 myhost ntpd[50297]: adjusting local clock by 519.109281s
> Dec 29 05:20:27 myhost ntpd[50297]: adjusting local clock by 518.792356s
>
> Right after it adjusts the local clock, I check, and it's still 518~
> seconds behind.
>
> This was with a stock ntpd config, and with one that I changed to use a
> local ntpd server.
>
> Am I doing something wrong?
>
> Thank you!
>
> -Henrich
>
ntpd is still adjusting the clock, which is aprocess that takes time
itself. Note that the offset printed will be lower each time.
-Otto
