BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Best practice for production servers: To reboot or not to reboot?

Subject: Best practice for production servers: To reboot or not to reboot?
From: robert-2x9W/xM/j7LR7s880joybQ at public.gmane.org (Robert La Ferla)
Date: Tue, 14 Sep 2010 14:30:11 -0400
In-reply-to: <AANLkTimPMYnTwHk2J1s7MiLYOdHDtWX93JNn6m+eNAyE-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
References: <1E2BC816-C308-4FD1-A7A4-CB50C7141ECF@laferla.net> <000001cb5400$8297c9f0$87c75dd0$@com> <AANLkTimPMYnTwHk2J1s7MiLYOdHDtWX93JNn6m+eNAyE@mail.gmail.com>

So now I'll refine my question. The servers that we're using are Solaris and are running various services including Java app servers, NFS, SMTP, and others. 

If a server isn't rebooted on say an annual basis, fsck doesn't get run. Drive mounts that were added but not made permanent won't get remounted. Configuration changes and network changes may affect the reboot. Given this, is it better to never reboot or reboot on a periodic basis.

References:
- Best practice for production servers: To reboot or not to reboot?
  - From: robert-2x9W/xM/j7LR7s880joybQ at public.gmane.org (La Ferla Robert)
- Best practice for production servers: To reboot or not to reboot?
  - From: blu-Z8efaSeK1ezqlBn2x/YWAg at public.gmane.org (Edward Ned Harvey)
- Best practice for production servers: To reboot or not to reboot?
  - From: jack-rp9/bkPP+cDYtjvyW6yDsg at public.gmane.org (Jack Coats)

Prev by Date: pfSense
Next by Date: Best practice for production servers: To reboot or not to reboot?
Previous by thread: Best practice for production servers: To reboot or not to reboot?
Next by thread: Best practice for production servers: To reboot or not to reboot?
Index(es):
- Date
- Thread


BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Boston Linux & Unix / webmaster@blu.org