On Tue, Jan 31, 2012 at 07:46:03PM +0100, Michael Biebl wrote: > I guess you don't have systemd-sysv installed, i.e. halt and shutdown > are provided by sysvinit? > > As already mentioned, you can either use systemctl directly or create a > /dev/log → /run/log symlink manually. > > Roger, would it be feasible if halt/shutdown could gracefully fallback > to /dev/log?
I don't think /dev/log is at issue here. I would hazard a guess that the sysvinit telinit/init binary is being invoked with "telinit (0|6)" and is trying to open /run/initctl, which does not exist and/or has no listener due to /sbin/init not being started when systemd is running. Assuming that the systemd socket listener is listening on /dev/initctl, it's simply not talking to the service. I would suggest that the systemd package switch to using the new sysvinit path, since if the service is there for backward compatibility with the sysvinit binaries installed on the system (I might be wrong here), it should be compatible with those. I'll look and see if we could add a fallback to sysvinit, but I would suspect not--it's simply hardcoded as a "#define INIT_FIFO ...." without any support for fallbacks. While we could add support, it gains us nothing from the sysvinit side. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `- GPG Public Key: 0x25BFB848 Please GPG sign your mail. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
