[CentOS] 2038 year Problem

[Gordon Messmer]

On 10/2/18 10:41 AM, Johann Fock wrote:
> Ist the 2038 year Problem solved in CentOS 7.5 64 bit Version


If you define the problem as the limitations of system clock based on a 
32-bit representation of seconds relative to the epoch, then the answer 
is "yes."  The Linux kernel uses a 64-bit clock on 64-bit systems.

Any given application may store dates in a format of its own choosing, 
though, so its possible that applications running on CentOS 7 could 
still have a problem.

It's probably easier and faster to simply set the system clock of a test 
host to the year 2040 and test the system and its applications than it 
is to ask for opinions, though.