Today I'm defensively coding for the year 2062 bug - a.k.a nanoseconds since epoch.

· · Web · 1 · 1 · 1

@stsquad I suppose you mean y2262 (int64_t ns since 1970), not y2062?

2262 is the latest that a current Linux kernel might survive, it's explicitly not trying to handle that in a number of cases that are easily fixed in a couple of centuries. (famous last words).

A lot of systems break much earlier when the real-time clock overflows the 100 year counter in 2070, or runs into the non-leapyear bug in 2100.

@arnd yeah I dropped a 2 when tooting. Surprisingly we can hit it quite quickly when simulating a IoT device that sleeps a lot with 's -icount sleep=off mode

@arnd @stsquad Last week I passed over the Millau viaduct, which has a design life of 120 years. Now I hear you thinking: "Do bridges care about year X bugs?". The interesting part here is the bridge's structural health monitoring system.

Sign in to participate in the conversation

General purpose mastodon instance