On Fri, 09.09.11 13:57, Marti Raudsepp ([email protected]) 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[1]: Reexecuting. > Sep 9 13:50:13 arch systemd[1]: 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[392]: shutting down for system reboot > Sep 9 13:50:16 arch systemd-initctl[387]: 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.
Hmm, something is sending an environment change request which we don't handle really. However, that should not be much of a problem since we just ignore that. But it appears as is from the on we are not handling things properly in the /dev/initctl handler. This is probably easy to fix (just some parse error in initctl.c), however not so much for me, since I am sysvinit-free since ages, and I am not sure I want to install sysvinit again to make this work. Try to use gdb on systemd-initctl and check if you can figure out where the service chokes on the commands. Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
