[PapaBear3625]

In 22 years, any unix/linux platform still using 32-bit timestamps will overflow:

From Wiki:

At 06:28:16 UTC on 7 Feb 2036, Network Time Protocol will loop over to the next epoch, as the 32-bit time stamp value used in NTP will overflow.

At 03:14:08 UTC on 19 January 2038, 32-bit versions of the Unix time stamp will cease to work, as it will overflow the largest value that can be held in a signed 32-bit number (7FFFFFFF16 or 2,147,483,647). Before this moment, software using 32-bit time stamps will need to adopt a new convention for time stamps,[19] and file formats using 32-bit time stamps will need to be changed to support larger time stamps or a different epoch.

At 06:28:15 UTC on Sun, 7 February 2106, the Unix time will reach FFFFFFFF16 or 4,294,967,295 seconds which, for systems that hold the time on 32 bit unsigned numbers, is the maximum attainable. For these systems, the next second will be incorrectly interpreted as 00:00:00 1 January 1970 UTC.

[Paladin2]

Time keeping on a stand alone real time system is always a problem that has to be managed. Remember that a one in a million calculation issue can occur every few seconds.

[Lazamataz]

Nobody will be alive in 2 years time, so no need to worry.

[Boogieman]

At some point, I predict it will just be cheaper to change our calendars to match whatever date the computers think it is, than to replace/patch all the computers :)

[FourtySeven]

I just realized something: Jan 19, 2038 is my theoretical date of retirement, according to the Social Security administration.

I wonder if that's going to be a problem...NAH, I'm sure the government has it all under control!