Date: Thu, 6 Feb 2003 19:51:48 +1100 (EST) From: Bruce Evans <bde@zeta.org.au> To: "Andrey A. Chernov" <ache@nagual.pp.ru> Cc: phk@FreeBSD.ORG, <current@FreeBSD.ORG> Subject: Re: Wrong date for DEVFS entries Message-ID: <20030206193118.T72545-100000@gamplex.bde.org> In-Reply-To: <20030205231106.GA2968@nagual.pp.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 6 Feb 2003, Andrey A. Chernov wrote: > On Wed, Feb 05, 2003 at 23:44:08 +0100, phk@freebsd.org wrote: > > > > >2) Feb 6 01:36 (boot time) > > >3) Feb 6 04:36 (+3 TZ future jump) > > > > These timestamps have been touched, and the clock has made a 3 hour > > jump either forward or backward at some point. > > > > The problem is the clock jump, not DEVFS. > > Clock jump happens as it supposed when adjkerntz(8) corrects machine clock > back to GMT via various CPU_* sysctl's. Could touched DEVFS stamps be > fixed back to something useful in the same sysctl code too? This should be well known to devfs users. devfs sets at least some of the times before adjkerntz can run, and nothing fixes them, so these times are wrong by the timezone difference. The problem is more obvious East of Europe since the timezone difference is positive and large. The bug has less noticable effects West of Greenwich since the difference is negative so the wrong timestamps are in the past. For me the difference is +10 or +11 hours so there is a 10 or 11 hour window after booting in which `ls -l /dev' and some periodic scripts report strangeness. There are related problems for boottime. These are hacked around in tc_setclock() by adjusting boottime when the time is changed. This works right when the time is changed soon after booting by adjkerntz or ntpdate but wrong after that. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030206193118.T72545-100000>