[systemd-devel] After upgrading glibc: Received environment initctl request
belxjander at gmail.com
Fri Sep 9 04:13:40 PDT 2011
I have had this behaviour ever since switching to systemd(21) on
SourceMage Gnu/Linux and have been working around it by deliberately
using "systemctl reboot" where it is configurable.
On Fri, 2011-09-09 at 13:57 +0300, Marti Raudsepp wrote:
> Dear list,
> I'm using systemd 35 on Arch Linux testing. Recently I had an upgrade
> for the glibc package and following that, I couldn't use sysvinit's
> /sbin/reboot -- the command would broadcast its message, wait for a
> few seconds and then quit. 'systemctl reboot' still works as supposed.
> This is what I get in syslog after upgrading glibc:
> Sep 9 13:50:13 arch systemd: Reexecuting.
> Sep 9 13:50:13 arch systemd: systemd 35 running in system mode.
> (+PAM -LIBWRAP -AUDIT -SELINUX +SYSVINIT +LIBCRYPTSETUP; arch)
> And when I issue /sbin/reboot:
> Sep 9 13:50:16 arch shutdown: shutting down for system reboot
> Sep 9 13:50:16 arch systemd-initctl: Received environment
> initctl request. This is not implemented in systemd.
> Tom Gundersen on #systemd reduced the problem down to this: "telinit u
> && reboot"
> When I run the above, I get into the same state that /sbin/reboot
> doesn't function.
> /sbin/reboot is owned by sysvinit 2.88-3
> It seems that another Arch Linux users has also experienced this
> problem: https://bbs.archlinux.org/viewtopic.php?pid=938398#p938398
> systemd-devel mailing list
> systemd-devel at lists.freedesktop.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 836 bytes
Desc: This is a digitally signed message part
More information about the systemd-devel