Yamaban composed on 2015-06-29 17:06 (UTC+0200):
auxsvr wrote:
After the latest glibc update, systemd crashed as I was restarting dbus, systemd-logind etc. The only way to resume normal operation was to restart the system. Has anyone else seen this?
In case the message did not make the way to you:
AFTER replacing a CORE library like glibc, do a RESTART asap.
Any other doing is provocing dataloss.
This begs a couple of questions: 1-What does "restart" mean? restart PID 1? reboot? kexec? something else? depends on context? 2-What's the point of kernel patching when "core" components are inducing "restarts"? http://kernelnewbies.org/Linux_4.0#head-9aa7c8499b42911a48c02b24f367bf2bc6db... -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org