Date: Mon, 29 Oct 2007 00:19:21 +0700 From: Eugene Grosbein <eugen@kuzbass.ru> To: Doug Barton <dougb@FreeBSD.org> Cc: stable@FreeBSD.org Subject: Re: CMOS, daylight saving time and dual-boot Message-ID: <20071028171921.GB18965@svzserv.kemerovo.su> In-Reply-To: <alpine.BSF.0.9999.0710281000330.33154@qbhto.arg> References: <20071028083955.GA69713@svzserv.kemerovo.su> <alpine.BSF.0.9999.0710281000330.33154@qbhto.arg>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Oct 28, 2007 at 10:02:11AM -0700, Doug Barton wrote: > >It was tuned off yesterday evening and turned back on today, > >loading FreeBSD. Meantime the switch from Summer Time to Standard Time > >has ocurred. There is 'ntpd_enable="YES"' in /etc/rc.conf. > >Nothing in a system reacted on the end of Summer Time period, > >so ntpd just complained about 3600 seconds exceeded sanity limit > >and bailed out (documented behavour). > > Right. You're looking at this as a DST problem, when in reality it's just > a "clock is too far off for ntpd to sync normally" problem. You want to > have a more general solution for that problem in any case. Adding > ntpd_sync_on_start to /etc/rc.conf is one way to accomplish that, there > are others of course. Suppose, the machine does not have global connectivity at all (and it has no local source of exact time) or just at the boot time. It still needs to adjust local time, right? It seems to me as DST problem really, not NTP problem. Eugene
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071028171921.GB18965>