top | item 22452698

(no title)

dictum | 6 years ago

Random thought: we're now closer to 2038 than to Y2K.

discuss

order

tempay|6 years ago

It's already here...I saw an issue a few weeks ago a bunch of production systems failed upon seeing a certificate signed by a CA root that expires after 2038.

function_seven|6 years ago

Or: We're now in the equivalent of 1982. Plenty of time to worry about it later!

martin-adams|6 years ago

and only heading in that direction

gumby|6 years ago

Speak for yourself.

ge96|6 years ago

what does this mean? you're okay if you're using 64bits? just briefly skimmed the 2038 wikipedia page, mentioned 32bit

onei|6 years ago

If you store time as seconds since the Unix epoch (1st Jan 1970), you'll overflow a 32 bit unsigned integer in 2038 (around March iirc) and time will suddenly be back in 1970 again. I believe the Linux kernel did some work to circumvent this on 32 bit systems in a recent release, but if you're running an old 32 bit system you're probably out of luck.