A near consensus has formed agreeing that it is a bad idea to delay reboot after patching. One reason is running apps rely upon the binaries and libraries that use the file(s) being patched. If they reference a certain offset in a file and that file has changed, the server will crash. Thanks to many including Christopher Barnard, David Stapleton, Andrew Caines, John Christian, and many more. Alan Rubin alan.rubin@csg.com.au -----Original Message----- From: sunmanagers-bounces@sunmanagers.org [mailto:sunmanagers-bounces@sunmanagers.org] On Behalf Of Alan Rubin Sent: Friday, 12 January 2007 8:58 AM To: sunmanagers@sunmanagers.org Subject: Patching and Reboots Hello, >From past experience, installing a recommended patch cluster can take up to 2 hours. Included with each cluster is almost always a patch which requires a reboot (such as a kernel patch). If we were to install the cluster during business hours but schedule a reboot/outage for after hours how would this affect the stability and function of the server? I will have to present plans for patching to a change management board - which should be a familiar practice to many on this list - and they will need to know the risks associated with such a plan. Regards, Alan Rubin alan.rubin@csg.com.au _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Tue Jan 16 17:21:33 2007
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:44:03 EST