On 2010/09/02 07:39 PM, Stephen Harris wrote: > On Thu, Sep 02, 2010 at 01:27:22PM -0400, Brian Mathis wrote: >> Uptime is no longer a badge of honor. Typically there will have been >> some kernel updates that require a reboot, so a long uptime means they >> haven't been applied. Also, it is a good idea to reboot periodically >> to catch anything that was not set up to start on boot correctly. A >> server should always cleanly start up with all services it needs >> without the need for human intervention. > Indeed. At my place we reboot production machines every 90 days. Or > are meant to; I don't think management have worked out that rebooting > 10,000 machines every 90 days means a lot of reboot activity!! > > (The idea being to verify that services will come up after some form > of DC-wide outage; last think we want in a "business contingency" situation > is a few hundred servers not working properly 'cos the rc scripts are > broken) Interesting..... This generally won't happen on a rock solid OS like CentOS, unless someone really screwed up badly or it's a super-custom build which can't be updated using normal CentOS repositories. We don't reboot servers (CentOS at least), unless we really really need to. For minor kernel updates that doesn't give much more than what we need we don't reboot either. Only for more critical / major / highly important kernel updates, or hardware upgrades do we reboot. -- Kind Regards Rudi Ahlers, SoftDux MD Website: http://www.SoftDux.com Blog: http://Blog.SoftDux.com Support: http://Billing.SoftDux.com Office: 087 805 9573 Cell: 082 554 7532 Fax: 086 609 6128 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20100902/4e41ae7f/attachment-0005.html>