"All three flight control modules on the 787 might simultaneously reset if continuously powered on for 22 days"http://www.seattletimes.com/business/boeing-aerospace/faa-orders-787-safety-fix-reboot-power-once-in-a-while/ …
-
-
Replying to @rygorous
"22 days" is muggle for "2^31 milliseconds", FWIW.
3 replies 67 retweets 122 likes -
Replying to @rygorous
(not really - it's 24.8 days - but close enough that I'm thinking that 2.8 days is the FAA's safety margin for this rule.)
3 replies 13 retweets 23 likes -
Replying to @rygorous
So we're back to Win95 levels of safety systems? Win95 overflowed after 49 days... and many programs crashed.
1 reply 0 retweets 7 likes -
Replying to @dascandy42
Win95 itself crashed on overflow. The function in question (GetTickCount) is still there, still overflows after 49.7 days,
1 reply 0 retweets 8 likes -
Replying to @rygorous @dascandy42
but it's not a problem with most programs. (Empirically speaking, since my machine often has >50 days uptime.)
1 reply 0 retweets 2 likes -
Replying to @rygorous
... When Win95 was common, programs used to crash on it. It's why the Linux kernel counter starts at Toverflow - 5 minutes.
1 reply 0 retweets 2 likes
Is that why Java has sleep(300) in its startup code?
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.