Hi Guys,
Well this helped sort of, the clocks are running only a little fast at
this point (roughly seven minutes gained over 12 hours), but now for
some reason, ntpd is not resetting the clocks at all, despite multiple
good time sources, it was working fine before the kern.hz change. Any
reason why that would break ntpd?
Thanks,
Jeff
Jeffrey Williams wrote:
Hi Guys,
Ok it is set, it does seem a little better, the clocks are still
running ahead by an average of about 30-40 seconds, but they seem to
have slowed down enough for ntpd to maintain the time by slewing,
instead of stepping. I did get a fresh batch of calcru errors from
one of the servers right after reboot (possibly because I am setting
kern.timecounter.hardware in sysctl.conf instead of loader.conf). I
will let you know how it looks after it has run for an hour or two.
I tried TSC instead of i8254 on a third server, it was better than
ACPI-safe, but much worse than i8254.
Thanks,
Jeff
Andrew Thompson wrote:
On Wed, Jan 21, 2009 at 12:30:26PM -0800, Jeffrey Williams wrote:
Hi Guys,
Thanks for kern.hz suggestion, but according loader.conf in the
/boot/defaults directory, kern.hz is already set to 100, is this
overridden somewhere else?
Thats a bit misleading, the commented out value isnt actually the
default. Set it in the loader.conf, can verify this with 'sysctl
kern.hz'
Andrew
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to
"freebsd-stable-unsubscr...@freebsd.org"
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
