SAM and kernel changes/swinstall and patches

[Tim Killinger]

Can anyone gues the reasoning behind SAM not allowing kernel changes without a reboot at that point int time?

It seems that it would be nice to be able to install patches or make kernel changes during the day and defer the reboot to non-production hours?

Am I missing something? Can a reboot be defered using SAM for kernel changes or swinstall for applying patches??

[Victor Fridyev · Accepted solution]

Hi,

You may postpone a shutdown after kernel update if choose this option in SAM after kernel rebuilding.

Re patche installation it's more or less clearly: such an operations updates both kernel and libraries. If not to reboot, you have to work with old kernel and new libraries, which may cause problems.

HTH

[Sยภเl Kย๓คг]

It is not advised to postpone the system reboot after installing the patch.If you are not restartinng the server it will use the old kernal but with newly patched files and libraries.Since your server is a production server install the patches at a no production time reboot the server to use the updated kernal to avoid malfuctioning or may be evevn a panic.

regrads
SK

[Muthukumar_5]

Kernel changes are differing as,

whole kernel configuration and loadable kernel modules.

whole kernel configuration are formed by generating static portions and dynamic loadable modules. In this situation we have to update the system and reboot to get the active of changes.

dynamic loadable modules updation does not require reboot because of dynamically updated values on the kernel parameters.

You can idenity the parameters informations with kmtune ( < 11.23 versions ) and kctune >=11.23.

Patches are being as same so that static portions needs to be updated and get reboot so that changes will be in Effect.