-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, Jun 02, 2005 at 09:50:22PM -0500, Bryan J. Smith wrote:
On Thu, 2005-06-02 at 21:34 -0400, James Olin Oden wrote:
While I agree with most of your points (the short and long version), I think that when you update software on your production servers during a maintenance window, its generally a good idea to do a reboot then to make sure that your not supprised years later.
I never disagreed with this. In fact, if you want to test for boot-time issues, the time to do it _is_ when you have upgraded some details _and_ are in that maintenance window.
Ehehehe that sounds like me breaking the build tree for Conectiva during development cycles. :)
I typically find that I'm maintaining a configuration management set whereby I have at least 1 system non-production and I can already test for this, and any variation in production. But if you're going to do it -- e.g., if you suspect that power or other interruptions will possibly occur -- then by all means, that _is_ the time to do it.
I second that recomendation.
I was just basically saying don't reboot just because you have a window. I always reboot my NT servers once a week, and I cringe to see new Linux administrators try to apply the same logic. ;->
You have NT servers ? I'm really sorry :P
[]s
- -- Rodrigo Barbosa rodrigob@suespammers.org "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)