Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

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?



On 09/15/2010 02:20 PM, Richard Pieri wrote:
> On Sep 15, 2010, at 2:12 PM, Jerry Feldman wrote:
>  =20
>> The bottom line is the reboot policy should be based upon what you are=

>> running.
>>    =20
> Which is what I wrote at the start.
>
>
>  =20
I agree, this was the consensus, but the OP was just looking for some
outside guidance. IMHO, if there is no reason to reboot, then don't. In
the very near future, we will be able to patch running kernels.

--=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








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

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org