On Sat, 2013-01-26 at 08:44 +0100, Philipp Matthias Hahn wrote: > Package: kexec-tools > Version: 1:2.0.3-2 > Severity: whishlist > > Since I switched to Systemd, /etc/init.d/kexec-load no longer works as I > expect. This is caused by /lib/lsb/init-functions being changed by > Systemd to integrate traditional LSB init scripts into how Systemd > works. > > My current work-around was to juse out-comment that line: > -- /tmp/x/etc/init.d/kexec-load 2013-01-12 23:04:53.000000000 +0100 > +++ /etc/init.d/kexec-load 2013-01-16 22:50:55.969207479 +0100 > @@ -13,7 +13,7 @@ > PATH=/sbin:/bin:/usr/sbin:/usr/bin > NOKEXECFILE=/tmp/no-kexec-reboot > > -. /lib/lsb/init-functions > +#. /lib/lsb/init-functions > > test -r /etc/default/kexec && . /etc/default/kexec > > That now produces some warnings about the log_* functions being no > longer found, but otherwise works okay (for me). > > I've done that because I like the easy way of just invoking > /etc/init.d/kexec-load stop > to load my next kernel after an kernel update, because that script > figures out the right name of the vmlinux and initrd files, and kernel > command line. I could do that by invoking kexec myself with the right > arguments, but I find the init script easier. > > It would be nice if the init script would work again with systemd > installed or if the logic would be moved to an sbin/ script callable by > hand.
I am struggling with a fix for this one. Commenting out ". /lib/lsb/init-functions" is not a solution since that causes all calls to log the actions of the script to fail. I would rather fix the problem you see with systemd. Can you give me more details on "....kexec-load no longer works as I expect"? Does the script fail to load the kernel? Do you see warnings? Can you send me the output of "/etc/init.d/kexec-load stop" without ". /lib/lsb/init-functions" commented out? Thanks, Khalid -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
