We all remember the hysteria over the supposed disasters the Y2K bug would cause. If you don’t remember that, you’re obviously very young and I resent your age.
Chris Marget wrote up a nice piece looking into a similar bug. It’s probably not going to by as hyped as Y2K, but it’s nonetheless important. Because of the 32-bit signed integer used in Unix-based systems, there’s a maximum value of 2.1 billion seconds in the “epoch”, before it basically runs out and started back over at the beginning with 10000000000000000000000000000000. That may sound like a lot, but it’s actually about 68 years. Since the Unix epoch begins on January 1, 1970, this means we’re due for an epoch reset around 2038.
Interestingly, the Network Time Protocol will run out two years earlier. It’s not due to having the epoch date start two years earlier. Instead, it’s because it uses an unsigned 32-bit integer to keep time, so it’s actually good for 4.2 billion seconds, but the base clock starts at 1900.
Probably won’t cause planes to fall out of the sky, but something to keep an eye on in the next decade or two!
Read more at: Epoch Rollover: Coming Two Years Early To A Router Near You!
- Remembrances of Interfaces Past: Firewire - June 26, 2017
- Windows 10 S and Ransomware - June 23, 2017
- Cloud Extensions, DevOps Models, and Playing with GUIs on Docker with Gestalt Cloud News 17.6 - June 22, 2017
- AMD’s Future in Servers: New 7000-Series CPUs Launched and EPYC Analysis - June 22, 2017
- PCIe versus Ethernet in a Composable System - June 22, 2017
- Managing Your IT Career – The On-Premise IT Roundtable - June 20, 2017
- Wavebox: All Your Web Apps Are Belong To Us - June 16, 2017
- Excelero’s NVMesh Magic - June 14, 2017
- A Quick Look at LinuxKit Packaging System - June 14, 2017
- Advice to Vendors: Know Your Identity - June 9, 2017