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!
- Microsoft Edge and the Great Virtual Machine Escape - March 24, 2017
- Five MacBook Pro Dongles That Make Me Sad - March 24, 2017
- A simple command allows the CIA to commandeer 318 models of Cisco switches - March 23, 2017
- FreeNAS Corral Notes & First Impressions - March 23, 2017
- Elastifile: How Bizur - March 23, 2017
- StarWind Gives You a Gateway to the Cloud - March 21, 2017
- Tech Field Day Gets Containerized at DockerCon and Cloud Field Day - March 20, 2017
- Intel Optane Enters the Market - March 20, 2017
- From Windows to Azure – A Change in Focus - March 17, 2017
- AppliedMicro’s X-Gene 3 SoC Begins Sampling: A Step in ARM’s 2017 Server Ambitions - March 17, 2017