[email protected] wrote: > > several years ago there was a flurry of unexpected failures when it was > discovered that the linux kernel had a bug that caused it to crash after > 497 days of uptime
Bang on ! I never understood the sysadmin pissing contest of 'uptime'. I have been patching my machines on a regular basis since my early days as a sysadmin, and I would not dream of not rebooting a system after patching, even if it isn't mandatory for that set of patch, simply to know that the patches have not broken the reboot process. In the early of SANs, I run into one storage vendor who would not plug their fiber into your machine until you had demonstrated that the machine could boot and come up clean - they claimed that they wasted too many hours helping customers fix their machine when it turned out it was actually broken before they even set foot in the datacentre. For a system (in the wider meaning of the term) to be uninterrupted, the logic has to be written at the application level, taking into consideration that hardware will fail. To go back to the original question, this was never a requirement nor a functionality of the ERPs I have come across so far. To contrast that, I can't remember last time google.com wasn't up. -- Yves. http://www.sollers.ca/ _______________________________________________ Discuss mailing list [email protected] http://lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
