Yeah, we don't keep time internally when powered off. The box boots and gets NTP servers via DHCP options and updates. Then it's ready to start the next stage. This is pretty normal for embdedded.
Year 2038 bug
Nathaniel Young
Dylan Hernandez
Thia isn't a solution at all, many devices need to know the real time. And almost every solution in this thread is retarded - you just need to extend the size of time_t but you can't do that for various reasons in a lot of cases and that's why there's a problem.
Chase Thomas
OpenBSD got away with it since nobody uses BSD, its going to a much harder time with Linux I'm afraid
Luke Cooper
...
Blake Clark
and lots of software break monumentally anyway because of the weird cyclic behaviour of time they didn't expect.
Cooper Myers
The thing is some systems CANNOT be updated. A good example are embedded devices.
Michael Ross
how about two integers nigga
Thomas Diaz
If your program keeps time by measuring the difference between 2 timestamps instead of counting steps independent of time_t value you've done something wrong
John Thompson
Please never write anything critical, user.
Noah Young
That breaks everything that relies on the time. The 2038 overflow would simply break a lot of things that rely on the time.