aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBruce Ashfield <bruce.ashfield@gmail.com>2022-05-08 23:19:32 -0400
committerBruce Ashfield <bruce.ashfield@gmail.com>2022-05-09 09:57:24 -0400
commit3f11bc1b6b56c503ca2b52826ce78151d287a1dd (patch)
treee0ec3b68f0c9d99501525264c0fe970c0807220b
parent973c8d0964c6f40338857efe5b8009b2f647d485 (diff)
downloadmeta-virtualization-3f11bc1b6b56c503ca2b52826ce78151d287a1dd.tar.gz
meta-virtualization-3f11bc1b6b56c503ca2b52826ce78151d287a1dd.tar.bz2
meta-virtualization-3f11bc1b6b56c503ca2b52826ce78151d287a1dd.zip
xen-tools: correct xencommons initscript for systemd
commit [xen-tools: don't declare xencommons as an initscript for systemd] was wrong in an amazing two ways. It has an extranenous } and it has inverted logic. The result is that xencommons is not being properly declared as an initscript for sysvinit, and hence we don't fully boot. It isn't a problem for most systemd configurations, so we were booting as the initscript wasn't firing. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
-rw-r--r--recipes-extended/xen/xen-tools.inc2
1 files changed, 1 insertions, 1 deletions
diff --git a/recipes-extended/xen/xen-tools.inc b/recipes-extended/xen/xen-tools.inc
index eabb8fa..d499977 100644
--- a/recipes-extended/xen/xen-tools.inc
+++ b/recipes-extended/xen/xen-tools.inc
@@ -717,7 +717,7 @@ INSANE_SKIP:${PN} = "already-stripped"
# configure init.d scripts
INITSCRIPT_PACKAGES = "${PN}-xend ${PN}-xen-watchdog ${PN}-xendomains ${PN}-devd"
-INITSCRIPT_PACKAGES += "${@bb.utils.contains('DISTRO_FEATURES', 'systemd', '${PN}-xencommons}', '', d)}"
+INITSCRIPT_PACKAGES += "${@bb.utils.contains('DISTRO_FEATURES', 'systemd', '', '${PN}-xencommons', d)}"
INITSCRIPT_NAME:${PN}-xencommons = "xencommons"
INITSCRIPT_PARAMS:${PN}-xencommons = "defaults 80"
INITSCRIPT_NAME:${PN}-xen-watchdog = "xen-watchdog"