On Fri, Mar 23, 2007 at 10:30:43AM -0400, Douglas Allan Tutty wrote: > > Yes, you must reboot and perform the upgrade. If you read the upgrade > > guide and get your ducks in a row you can be all done *easily* in 30 > > minutes. If there were some kind of contest with cash prizes it could > > probably be done much quicker. However, it's much more important to get > > the steps right than to do it quickly, IMHO. > > So on a production machine, it has to be off-line for 30 minutes every > six months (not complaining, just clarifying).
In practice it should be less than that. But yes, following the normal process you will have downtime/reboots every six months for upgrading. If you search the archives for this list, you'll find WAY TOO MUCH discussion about uptime and rebooting. I'll condense it for you: it's OK to reboot and 'ruin' your uptime for scheduled maintenance. Bragging about uptime means your system is unpatched. If you have critical systems that can't be down for upgrades, then you need redundant servers anyway. In which case you upgrade one at a time. ;) -- Darrin Chandler | Phoenix BSD User Group | MetaBUG [EMAIL PROTECTED] | http://phxbug.org/ | http://metabug.org/ http://www.stilyagin.com/ | Daemons in the Desert | Global BUG Federation
