Re: ntpd doesn't keep good time

[Brian <bri@sonicboom.org>]

Tried firing ntpq, then pe within that to see what it thinks of the
servers you've specified?


	Brian

The path to a desireable destination
is often more difficult than the path to stay where you are.

On Wed, 20 Aug 2003, Robert Connolly wrote:

> I'm getting weird behaviour from ntpd:
> Aug 20 22:02:20 Insanity ntpd[7649]: time reset +0.521183 s
> Aug 20 22:18:43 Insanity ntpd[7649]: time reset +0.338957 s
> Aug 20 23:19:13 Insanity ntpd[7649]: time reset -0.249005 s
> Aug 20 23:24:51 Insanity ntpd[7649]: time reset -0.411547 s
> This is happening constantly on 2 of my obsd boxes. Neither of them will stay
> still. Im running current with ntpd-4.1.74 from ports. Im not using ntpdate,
> I am using ntpd -g -q instead from rc.securelevel. Aswell I found it helped
> to add -t 9995 to tickadj in rc.securelevel. One box is a pentium 90mhz,
> second is a duron 800. Last night the pentium 90 ntpd stepped ahead 14
> seconds. I added a half dozen public servers to both config files and
> rebooted both.
> Anyone know why my time wont stay still?
>