Date: Sat, 27 Apr 2019 23:36:55 +0200 From: Matthias Oestreicher <matthias@smormegpa.no> To: freebsd-questions@freebsd.org Subject: Re: Help with ntpd Message-ID: <69a9b22504a6959cb2ed74b5e415d24202d7eed5.camel@smormegpa.no> In-Reply-To: <214f5bcb-8c38-5be3-9aaa-00c7bc83a79f@missouri.edu> References: <62834f37-f517-9807-9303-584cdacddc31@missouri.edu> <407c771d-070c-b4d8-bf53-d14c60689258@radel.com> <214f5bcb-8c38-5be3-9aaa-00c7bc83a79f@missouri.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 2019-04-27 at 21:13 +0000, Montgomery-Smith, Stephen wrote: > 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. I could imagine your BIOS battery is dead. Does the file /etc/wall_cmos_clock exist? If yes, set the BIOS clock to your local time. If not, set your BIOS clock to GMT. Hope that helps -Matthias > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?69a9b22504a6959cb2ed74b5e415d24202d7eed5.camel>