Date: Tue, 26 Feb 2019 20:13:36 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 236065] TimeStamp Overflow 2106 year Message-ID: <bug-236065-227-mtOPNQrJ2e@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-236065-227@https.bugs.freebsd.org/bugzilla/> References: <bug-236065-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D236065 Conrad Meyer <cem@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |Not Enough Information Status|New |Closed --- Comment #1 from Conrad Meyer <cem@freebsd.org> --- How are you setting the date and reading the date? FreeBSD does use 64-bit for time_t on amd64, but cannot control the hardware clock's range. Given you observe the correct date prior to reboot, I think we're probably doing the right thing in the OS. I believe the lost range after reboot is due to a limitation of your PC hardware's clock (atrtc(4)), which uses two digits of binary-coded decimal = for the year; years wrap at exactly 100 years, which is what you observed. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-236065-227-mtOPNQrJ2e>