Date: Sat, 27 Apr 2019 21:13:09 +0000 From: "Montgomery-Smith, Stephen" <stephen@missouri.edu> To: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Help with ntpd Message-ID: <214f5bcb-8c38-5be3-9aaa-00c7bc83a79f@missouri.edu> In-Reply-To: <407c771d-070c-b4d8-bf53-d14c60689258@radel.com> References: <62834f37-f517-9807-9303-584cdacddc31@missouri.edu> <407c771d-070c-b4d8-bf53-d14c60689258@radel.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/27/19 1:21 PM, Jon Radel wrote: > On 4/27/19 13:30, Montgomery-Smith, Stephen wrote: >> For some reason, ntpd has stopped correcting the time on my FreeBSD >> computer. After 12 hours, my clock has fallen back 4 hours! So it is >> very serious. >> > Does it then stabilize at 4 hours precisely? In Missouri, which I > believe is currently at 4 hours offset from UTC? I think the time difference between Missouri and UTC is 5 hours. > > If so, I'd suggest that you've done something unfortunate with your > timezone and related settings, though personally I'm having trouble > coming up with a model where ntpdate gives you the result you expect and > ntpd doesn't. What timezone do your kernel clock and your CMOS/hardware > clock believe they're in? Everything should be local time. This is the only OS on this computer.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?214f5bcb-8c38-5be3-9aaa-00c7bc83a79f>