On Wednesday 18 February 2015, Michael J Dur wrote:
Hello Moby,
There is a bug open that is the explanation for this behaviour. You can read the details here:
https://bugzilla.opensuse.org/show_bug.cgi?id=918226
For the moment you can go back to the previous version of systemd (and add a lock so it doesn't upgrade until the fix is out) with this command:
zypper -n in --oldpackage systemd-32bit-208-23.3.x86_64 systemd-208-23.3.x86_64 systemd-sysvinit-208-23.3.x86_64 && zypper al systemd-32bit systemd systemd-sysvinit
Regarding this workaround. How could I safely reboot such affected system? Or at least stop services to remount ro etc. $ shutdown -r now Failed to open /dev/initctl: No such device or address Failed to talk to init daemon. $ systemctl stop named Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: Connection refused Even killing a deamon does not work anymore: $ killall named $ ps aux | grep named named 2027 0.0 0.0 0 0 ? Zs Feb18 0:20 [named] <defunct> cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org