Red HatThis forum is for the discussion of Red Hat Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a bunch of CentOS 5.5 servers which are in production use. I would like to know what actually happens underneath when I update them.
Running an yum update (pointing to the default repos) will update to CentOS 5.8. Now, during the update process, say apache httpd v 2.2.2 is running live serving pages while at the same time I run yum update and it updates the apache httpd to v 2.2.3. Seems like a very obvious question, but does the it restart the httpd service?
Also, updating from CentOS 5.5 to 5.8 would it matter if I not reboot the machine. A reboot will pick the latest installed kernel but other than that is it ok to keep the server running without a reboot?
Last edited by the_gripmaster; 05-29-2012 at 12:27 AM.
I personally would be very hesitant to update & not reboot asap in a production environment, as I have had unexplained problems after upgrading & not rebooting in the past. Any chance you can test this in a DEV environment first?
I personally would be very hesitant to update & not reboot asap in a production environment, as I have had unexplained problems after upgrading & not rebooting in the past. Any chance you can test this in a DEV environment first?
Not really. I did update the dev environments but had rebooted soon after the yum update.
Yes, now I realize there could be issues not rebooting after such a major leap in versions.
If Yum upgrades httpd, it will definitely restarts httpd since it erases existing version and installs the new one. This scenario, you do not require reboot.
If you upgrade the system packages like kernel etc, you must need to reboot the system.
So after apache (httpd) is updated, the older version is still in memory and it is the one running. A restart of the service will load the updated binaries/libraries.
If you upgrade the system packages like kernel etc, you must need to reboot the system.
I don't believe its mandatory to reboot the system after kernel upgrade, but if you install a new kernel then you need to reboot your machine from the new kernel.
I don't believe its mandatory to reboot the system after kernel upgrade, but if you install a new kernel then you need to reboot your machine from the new kernel.
Correct. Yum always "installs" (rather than update) a new kernel. So it is okay not to reboot unless you want to run using the latest installed kernel.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.