|
|
Sponsored Content
Homework and Emergencies
Emergency UNIX and Linux Support
Different OS Kernel Update Frequency
Post 302555822 by majid.merkava on Thursday 15th of September 2011 05:25:49 PM
09-15-2011
Quote:
Disclaimer: I can only attest for the Linux side of things here.
First of all, 3 to 6 months isn't that long of an uptime, as I've seen systems with 2+ years. And with the distributions you've listed there won't be any major kernel updates in that time, save important security updates, and even those don't force a reboot (but the new kernel will only be used after a reboot). If you really need high availability, better to look into proper redundancy by setting up a cluster, where a second node can easily take over should the primary suffer a hardware defect.
First of all, 3 to 6 months isn't that long of an uptime, as I've seen systems with 2+ years. And with the distributions you've listed there won't be any major kernel updates in that time, save important security updates, and even those don't force a reboot (but the new kernel will only be used after a reboot). If you really need high availability, better to look into proper redundancy by setting up a cluster, where a second node can easily take over should the primary suffer a hardware defect.
. On my home server I use CentOS but i see that there is a kernel update each month. Should I reboot each time? Where could I find information about each update. Is it a security or a normal and I can postpone reboot.|
|
7 More Discussions You Might Find Interesting
1. Linux
Hi All,
I need to update my redhatas4 kernel with kernel-2.6.9-67.0.20.EL.src.rpm.
When I run this
# rpm -ivh kernel-2.6.9-67.0.20.EL.src.rpm
warning: user brewbuilder does not exist - using root
warning: group brewbuilder does not exist - using root
warning: user brewbuilder does... (2 Replies)
Discussion started by: itik
2 Replies
2. Solaris
Hi All,
I am installing kernel Update 3.0 in my Solaris servers.
It actually installs most of the patches in this update , but for some packages it is not installing.
It is saying ...
Version of package SUNWcakr from directory SUNWcakr.us in patch 137137-09 differs from the package... (7 Replies)
Discussion started by: jegaraman
7 Replies
3. Solaris
Hi I am installeing Solaris Kernel update in my solaris Server.
The Solaris Kernel update skipps the patch 120011-14.
saying that it had already been installed.
But it is not found in /var/sadm/patch directory where all the patches will be there.
And also i could not install other... (11 Replies)
Discussion started by: jegaraman
11 Replies
4. Red Hat
1. Where do i obtain new kernels in ".rpm" format to update my RHEL5?
is it only available to RHN subscribers?
2. i downloaded latest kernel (linux-2.6.31.5.tar.bz2) from kernel.org.
#tar -xjvf linux-2.6.31.5.tar.bz2
after this i have a directory with lots of stuff in there. how do... (2 Replies)
Discussion started by: dplinux
2 Replies
5. Solaris
tell me the step by step procedure for updating the kernel patches in solaris 10. (1 Reply)
Discussion started by: tv.praveenkumar
1 Replies
6. Red Hat
Dear all,
I have some linux servers in my prod environment. For two years i have not done any kernel updates or required patches ...should i have to this activity. My kernel version is 2.6.18-164.el5xen and linux release is release 5.4 (Tikanga).
And reboot also not done for 2 years is... (2 Replies)
Discussion started by: jegaraman
2 Replies
7. UNIX for Dummies Questions & Answers
Hi
i want know to how to check NTP update frequency for a server?
what should be its ideal value or range ?
also, i have configure one switch and on gui i can see NTP update frequency value is 1440. also no idea what should be its ideal value
i am not sure if this is correct or not .... (1 Reply)
Discussion started by: scriptor
1 Replies
LEARN ABOUT MINIX
reboot
REBOOT(8) System Manager's Manual REBOOT(8) NAME
reboot - reboot the system immediately SYNOPSIS
reboot [-f] DESCRIPTION
Reboot can be used to reboot the system after installing a new kernel. It does not inform the users, but does log it's actions in /usr/adm/wtmp and /usr/adm/authlog. The system is then rebooted with the reboot(2) systemcall. If the -f flag is not given then all processes are sent terminate signals to give them a chance to die peacefully before the reboot() call. If the wtmp file exists, reboot logs itself as if it were a shutdown. This is done to prevent last(1) from talking about system-crashes. Reboot is registered as is in the authlog file. Reboot can only be executed by the super-user. Any other caller will be refused, either by reboot(8) or by reboot(2). SEE ALSO
reboot(2), shutdown(8), halt(8), boot(8). BUGS
The error message's given by reboot are not always useful. There are several routines that can fail, but which are not fatal for the pro- gram. AUTHOR
Edvard Tuinder (v892231@si.hhs.NL) REBOOT(8)