4 ms·
This was to avoid the bug in NT where the servers, if they hadn't crashed already, would crash for sure at the 49.7 day mark. This bug took down air traffic co
by astrodust 13y ago
This was to avoid the bug in NT where the servers, if they hadn't crashed already, would crash for sure at the 49.7 day mark.
This bug took down air traffic control computers: http://news.techworld.com/operating-systems/2275/microsoft-server-crash-nearly-causes-800-plane-pile-up/ http://news.techworld.com/operating-systems/2275/microsoft-s...
- stcredzero 13y ago> would crash for sure at the 49.7 day mark. That's not so bad. So long as they have the option to skip this week's reboot, this shouldn't be a problem in combat. (They should've randomized the reboot schedule so that an enemy couldn't exploit it.)
- chris_wot 13y agoYeah, except if they were attacked 49.7 days after the last reboot.
- recursive 13y agoSuch a time wouldn't exist.
- derleth 13y ago> Such a time wouldn't exist. It seems you could get close to ensuring such a time would exist by creating constant emergencies for the crew to deal with such that rebooting would be hazardous, and waiting for the reboot-or-crash date to launch the major attack.
- stcredzero 13y agoWhat would seal the deal would be if there was some external signal that revealed that the crash happened. This could be as easy to arrange as a confederate onboard with a powerful laser pointer.