5 ms·
Since we're talking about aviation, that same overflow bug caused a meltdown of Southern California air traffic control in 2010 after someone forgot to preempti
by agwa 12y ago
Since we're talking about aviation, that same overflow bug caused a meltdown of Southern California air traffic control in 2010 after someone forgot to preemptively reboot their Windows servers every 30 days: http://www.techworld.com/news/operating-systems/microsoft-server-crash-nearly-causes-800-plane-pile-up-3577711/ http://www.techworld.com/news/operating-systems/microsoft-se...
- bliti 12y agoStupid question to those who work in the aviation industry: This seems like a candidate for an automated script that reboots the server every n days or hours. Would such script be considered a potential risk? If so, why?
- reitanqild 12y agoAll of a sudden you have an emergency going on and a plane coming in in the middle of the night even though the airport is usually only open until 2100. And there goes the servers because of a stupid script. :-] Of course they went down anyway and by the far more likely cause of forgetting to reboot.
- jkot 12y agoToday it is even better. 2GB of updates will get applied after rebooting, before system starts.
- digi_owl 12y agoAnd that is why WSUS exists...
- thirdsun 12y agoThere was a story recently about a german 2nd division basketball team that ran their scoreboard on Windows and applied updates about an hour before the game - scoreboard wasn't back up in time, team lost since the match couldn't start within the allowed timeframe and of course this match was important, kind of an endgame and the loss led to the relegation of the team.
- tw04 12y agoWhich is why you have redundant systems. The scheduled updates allow you to validate that both are working so that in the event of an unplanned downtime, you aren't stuck scrambling to figure out why the redundant system doesn't function at all.
- HeyLaughingBoy 12y agoWell, there is the problem of how you use the server while it's rebooting...