-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-02-08 03:01, John Andersen wrote:
On 02/07/2015 05:54 PM, Carlos E. R. wrote:
I'll go you one better..... It should recommend either a logout and in again, or a reboot anytime there is any thing running modules that have been deleted. The message could say either reboot or logout depending on who has the modules locked.
It is not as clear cut as that. The actual action to do differs, depending on what was updated. Sometimes log out/in is the thing to do. Sometimes some system services need to be restarted, while log off/in does nothing, or not enough. Often the exact sequence of subsystems to be restarted is not easy to determine; often "init 3 ; init 5" does it, but others the trick is going to level 1 and back to 5. All that to avoid a reboot, which although being most often an overkill, it is the only thing that always works. Thus it is the admin which has to determine what to do. Zypper helps by suggesting you run "zypper ps" in order to find out what may be affected. Only on some crucial updates it suggests a reboot. But they forget to suggest that with glibc. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlTWyNIACgkQja8UbcUWM1x47QD/dX8qPD4RLM0SU6UKGY4D+RYa kmSW4TA2IHFthvzQpx0A+gIgb2oB4lq9PSs7IQA6n50VgN7+3UZ03qCK2vTKWblg =18P4 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org