| |||||||||||||
KHB: Recovering Device Drivers: From Sandboxing to SurvivingKHB: Recovering Device Drivers: From Sandboxing to SurvivingPosted Jan 18, 2007 12:08 UTC (Thu) by tsr2 (subscriber, #4293)Parent article: KHB: Recovering Device Drivers: From Sandboxing to Surviving
From the point of view of a web server, a crashed system and a system with no network access due to a safely sandboxed but crashed network driver are practically identical. I do not agree that they are practically identical. A crashed system will usually reboot and return to operation in a short period of time. A system that stays up, but is unable to communicate with the outside world will require external intervention. Also, if it's in an inconvenient location, you can't log in remotely and reboot, so all in all a crash is probably preferable in this scenario.
(Log in to post comments)
KHB: Recovering Device Drivers: From Sandboxing to Surviving Posted Jan 18, 2007 18:05 UTC (Thu) by bronson (subscriber, #4806) [Link] ...which was Val's point. If you want to split hairs, I think she meant, "From the point of view of a web server, a *hung* system and a system with no network access due to a safely sandboxed but crashed network driver are practically identical."
If a crashed system magically reboots, consider yourself very lucky. The majority of crashers that I've seen result in zombies computers unable to, say, read from its disk array. Until the watchdog steps in, of course, but a watchdogs work just fine for sandboxed systems too. Automatically-rebooting crashes are so 1990s.
I don't think the two situations are quite as different as you imply.
|
|||||||||||||