summaryrefslogtreecommitdiffstats
path: root/recipes-networking/openvswitch/files/openvswitch-controller-setup
diff options
context:
space:
mode:
authorMark Asselstine <mark.asselstine@windriver.com>2015-09-10 13:59:01 -0400
committerBruce Ashfield <bruce.ashfield@windriver.com>2015-09-10 14:42:43 -0400
commit9f177c12d8361341853fe9c34f6c5b8df3cbcc1a (patch)
tree7fa7a110e7bb6c9ffe736b9d9fccf2782e3fe297 /recipes-networking/openvswitch/files/openvswitch-controller-setup
parentc3c4d977cbb51363f9030c2e39d56a772b29f73b (diff)
downloadmeta-virtualization-9f177c12d8361341853fe9c34f6c5b8df3cbcc1a.tar.gz
libvirt: enable systemd support
Commit d114a62dd8a2121fa3026b83c5b250eb0ee6f21d [libvirt: kill update-rc.d when not using sysvinit] resulted in libvirt services not starting automatically at boot when using systemd. The upstream libvirt package already has the necessary systemd service files so it is just a matter of activating them via the '--with-init-script' configure option and making the recipe use these. We always set '--with-init-script' to 'systemd' regardless of the systemd vs sysvinit DISTRO_FLAG since our sysvinit scripts are external and thus not affected by this setting when building for sysvinit. Both sysvinit and systemd packages will be libvirt-libvirtd, the bbclasses ensure that only the files for one init system will exist in the package, so this 'overloading' is acceptable. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Diffstat (limited to 'recipes-networking/openvswitch/files/openvswitch-controller-setup')
0 files changed, 0 insertions, 0 deletions