New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Do nothing, hope nothing breaks. In the past some java applications didn't handle it well, but hopefully these bugs were already fixed.
Sit back, grab a beer and watch the Y2K madness!
It has little effect on me.
good video for anyone (like me) who didn't know the significance of this
https://en.wikipedia.org/wiki/Year_2038_problem bigger problem imo
The right want to handle it is to ignore it and let ntpd fix it.
Not surprisingly, OpenBSD handles it the right way.
The wrong way is to try to get fancy.
Not surprisingly, Linux tries to get fancy.
https://tools.ietf.org/html/rfc2550
Right for some people, certainly not everyone though. For checking differences between times, does that mean OpenBSD ignores leap seconds? Anyway your time is going to be off for the few hours that it takes to sync with ntpd, which may be undesirable for some applications. Either way you do it, it's not going to affect most users; and time-critical applications are still going to have to have something special to compensate.
"Similarly, 64-bit and 128-bit systems also will
fail, although somewhat later (after December 31, 922,337,203,685,477
and December 31, 17,014,118,346,046,923,173,168,730,371,588,410
respectively)."
lol
yup. . already past.