[CentOS] 2038 year Problem

Tue Oct 2 20:45:47 UTC 2018
J Martin Rushton <martinrushton56 at btinternet.com>

If you do that make sure it's a system you're happy to junk and
reinstall.  I have painful memories of trying to sort out systems we
rolled forward over Y2K.  Amongst other things the license manager
became convinced we were trying to fiddle things. :-(

On 02/10/18 20:07, Gordon Messmer wrote:
> 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.
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> https://lists.centos.org/mailman/listinfo/centos

J Martin Rushton MBCS

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL: <http://lists.centos.org/pipermail/centos/attachments/20181002/135813e9/attachment-0005.sig>