Joel Duckworth
May 22nd, 2008, 07:31 PM
Hi,
Does any know how to check if a restart is required after performing an upgrade from the command line?
I suspect that restarts are required for the same packages that require restarts on the desktop edition.
Thanks!
kidders
May 24th, 2008, 03:45 AM
Hi there,
It would be unreasonable to require a reboot on a server. Having said that, there are some occasions when rebooting might be a good idea. For example, if an update installs a kernel fix you want to take advantage of right away, you'll often need to reboot in order to do so. Similarly, performing updates to certain system libraries could cause odd behaviour if you don't reboot, depending on what you've installed, and where the software came from.
In general though, restarting individual services impacted by an update (which the install process tends to do for you anyway) is sufficient.
I would say that server admins are expected to recognise situations where a reboot is necessary to keep their box happy. If in doubt, performing software updates on a scheduled basis (and always rebooting, regardless of what gets updated) is probably best. That way, your users can expect not to have access to your box's services for a few minutes, and the next time your server does something weird, you can be sure that it's not simply because you updated package X three months ago, and didn't reboot.
vBulletin® v3.8.4, Copyright ©2000-2012, Jelsoft Enterprises Ltd.