Software glitch brings Y2K deja vu
-
"Software running on thousands of computers worldwide will become inoperable in a few weeks because of an obscure date-related glitch, and developers are rushing to create and apply patches." This affects some Unix systems. Full Story[^] Steve
-
"Software running on thousands of computers worldwide will become inoperable in a few weeks because of an obscure date-related glitch, and developers are rushing to create and apply patches." This affects some Unix systems. Full Story[^] Steve
There's a reason for ya to use
unsignedevery now and then.. :rolleyes: -- "We shall crush you down to the point, where there is no coming back, things will happen to you from which you could not recover if you lived a thousand years, a thousand years." -
There's a reason for ya to use
unsignedevery now and then.. :rolleyes: -- "We shall crush you down to the point, where there is no coming back, things will happen to you from which you could not recover if you lived a thousand years, a thousand years." -
"Software running on thousands of computers worldwide will become inoperable in a few weeks because of an obscure date-related glitch, and developers are rushing to create and apply patches." This affects some Unix systems. Full Story[^] Steve
I don't quite get it. i read the article and came across this line: The flaw involves the way the programs handle date entries, Gavaghan said. To be able to recognize dates, PTC programmers had to set a date for infinity. They chose 2 billion seconds since 1970 That number brings PTC software up to Jan. 10. After that, the software will be unable to recognize dates and will no longer operate. When I did the math, I only came up with 1073088000 seconds between Jan 1st, 1970 and Jan. 1st 2004. You wouldn't hit 2 billion until 2033. But they did offer this reassurance: It's not something where they would lose data," Gavaghan said. "The software just stops working.
Have you answered an MTQ? Check out the stats!
What's the latest butt-scratch count? Check it out! -
I don't quite get it. i read the article and came across this line: The flaw involves the way the programs handle date entries, Gavaghan said. To be able to recognize dates, PTC programmers had to set a date for infinity. They chose 2 billion seconds since 1970 That number brings PTC software up to Jan. 10. After that, the software will be unable to recognize dates and will no longer operate. When I did the math, I only came up with 1073088000 seconds between Jan 1st, 1970 and Jan. 1st 2004. You wouldn't hit 2 billion until 2033. But they did offer this reassurance: It's not something where they would lose data," Gavaghan said. "The software just stops working.
Have you answered an MTQ? Check out the stats!
What's the latest butt-scratch count? Check it out!I suspect they use a resolution of less than 1 second per unit - perhaps 500 ms per unit? Steve
-
I suspect they use a resolution of less than 1 second per unit - perhaps 500 ms per unit? Steve
Nope. The UNIX timestamp has a resolution of 1 second so that it is "portable". -- "We shall crush you down to the point, where there is no coming back, things will happen to you from which you could not recover if you lived a thousand years, a thousand years."
-
I don't quite get it. i read the article and came across this line: The flaw involves the way the programs handle date entries, Gavaghan said. To be able to recognize dates, PTC programmers had to set a date for infinity. They chose 2 billion seconds since 1970 That number brings PTC software up to Jan. 10. After that, the software will be unable to recognize dates and will no longer operate. When I did the math, I only came up with 1073088000 seconds between Jan 1st, 1970 and Jan. 1st 2004. You wouldn't hit 2 billion until 2033. But they did offer this reassurance: It's not something where they would lose data," Gavaghan said. "The software just stops working.
Have you answered an MTQ? Check out the stats!
What's the latest butt-scratch count? Check it out!Probably just inaccurate reporting; it's unlikely to be 2 billion, it'll be 2^31-1 = 2147483647, i.e. max positive range of a signed 32-bit integer. Which represents the date when Unix times break, in 2038. Not 4 billion. One way to buy a few more years would be to make time_t unsigned so it would go up to 2^32-1 = 4294967295. Or go 64-bit which buys you considerably more time! They probably saw the 2 billion somewhere, then saw this company's software broke halfway to that and doubled instead of halving. 2^30-1 is 1073741823, which matches up.
Andy Hassall (andy@andyh.co.uk) Space - disk usage analysis tool
-
"Software running on thousands of computers worldwide will become inoperable in a few weeks because of an obscure date-related glitch, and developers are rushing to create and apply patches." This affects some Unix systems. Full Story[^] Steve