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

[gaf-mNDKBlG2WHs at public.gmane.org (Jerry Feldman)]

On 09/14/2010 02:49 PM, Dan Ritter wrote:
> On Tue, Sep 14, 2010 at 02:30:11PM -0400, Robert La Ferla wrote:
>  =20
>> So now I'll refine my question. The servers that we're using are Solar=
is and are running various services including Java app servers, NFS, SMTP=
, and others.=20
>>
>> If a server isn't rebooted on say an annual basis, fsck doesn't get ru=
n. Drive mounts that were added but not made permanent won't get remounte=
d. Configuration changes and network changes may affect the reboot. Given=
 this, is it better to never reboot or reboot on a periodic basis.=20
>>    =20
>
> It is good to never have to reboot.
>
> It is better to reboot in a controlled situation when you have
> time to recover from entropy.
>
> It is best to have systems automation sufficient to prevent having
> temporary drive mounts, unexpected config changes, and so forth.
>
> -dsr-
>
>  =20
Didn't I just say this :-)

--=20
Jerry Feldman <gaf-mNDKBlG2WHs at public.gmane.org>
Boston Linux and Unix
PGP key id: 537C5846
PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB  CA3B 4607 4319 537C 5846