[Bug 236065] TimeStamp Overflow 2106 year

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Tue Feb 26 19:51:56 UTC 2019


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236065

            Bug ID: 236065
           Summary: TimeStamp Overflow 2106 year
           Product: Base System
           Version: 12.0-STABLE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: bin
          Assignee: bugs at FreeBSD.org
          Reporter: everton.win32 at gmail.com

Hi, are you ok?
I work doing tests, and I found one possible in a decentralized system that is
used worldwide.
I want to simulate a specific date in the 22nd century;
however when I define the system with the date: 01/01/2106 00:00; 

the system reports an error. 

if I enter another date, for exemple: 01/01/2105 00:00 
the freebsd allows it to be changed. 

but after the reboot. it sets to: 01/01/2005 00:00;

I found some information on:

https://en.wikipedia.org/wiki/Year_2038_problem 

there is a possibility that I compile the system to use the size uint64? 

according to the wikipedia topic:

FreeBSD uses 64-bit time_t for all 32-bit and 64-bit architectures except
32-bit i386[11].

if the field actually has 64 bits, it can even be used after 2107 (which is the
date I need);

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-bugs mailing list