"The Ghost In The Machine" <ewill@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:eckn04-mcp.ln1@xxxxxxxxxxxxxxxxxxxxxxxxxx
> In comp.os.linux.advocacy, Oliver Wong
> <owong@xxxxxxxxxxxxxx>
> wrote
> on Fri, 20 Oct 2006 17:42:41 GMT
> <lU7_g.28081$H7.2714@edtnps82>:
>> "Roy Schestowitz" <newsgroups@xxxxxxxxxxxxxxx> wrote in message
>> news:1161361646.884792.131240@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>>>
>>> Sounds nearly as bad as those patients with open bodies whose
>>> surgons waits for the Windows system to recover from a
>>> crash (yes, I have citations, Oliver).
>>
>> Can you post them? Do you know for sure that they're *Windows*
>> systems?
>>
>> - Oliver
>>
>
> I'm having problems finding anything using Google here
> but I did find this little tidbit; apparently a computer
> crash on Christmas Day, 2004 stranded 30,000 passengers.
> The headlines are mildly interesting:
>
> How It Happened: Onslaught overtaxed an old computer
> http://www.cincypost.com/2004/12/28/comp12-28-2004.html
>
> Problems at airports leave passengers stranded, luggage lost
> http://abclocal.go.com/wls/story?section=News&id=2551316
>
> Thousands of travelers cope with holiday headaches
> Comair grounded for weekend; US Airways deals with lost bags
> http://www.cnn.com/2004/TRAVEL/12/25/flights.canceled/index.html
>
> There is the issue that this might be a Comair problem, not a Microsoft
> Windows problem.
>
> This sort of thing probably cost the airline industries
> at least $3M in indirect costs, assuming $100 per ticket.
I remember reading about this a while ago (on Slashdot, perhaps?) I
believe they said it was something about the giving each piece of luggage a
unique ID, and ending up with a integer overflow (I.e. more than 32767
pieces of luggage were in the system simultaneously, or something).
- Oliver
|
|
