From: He Zhe <[email protected]> The systemd service needs to be tuned according to various use cases and cannot be able to always start successfully for example when there is no network interface named br0 by default.
Thus the default configuration is mainly used as an example. Let's not automatically start it on boot. Signed-off-by: He Zhe <[email protected]> --- recipes-connectivity/consul/consul_git.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/recipes-connectivity/consul/consul_git.bb b/recipes-connectivity/consul/consul_git.bb index f3e64e9..566fbc9 100644 --- a/recipes-connectivity/consul/consul_git.bb +++ b/recipes-connectivity/consul/consul_git.bb @@ -25,7 +25,7 @@ inherit systemd go COMPATIBLE_HOST_mipsarch = "null" SYSTEMD_SERVICE_${PN} = "consul.service" -SYSTEMD_AUTO_ENABLE_${PN} = "enable" +SYSTEMD_AUTO_ENABLE_${PN} = "disable" do_install_append() { install -d ${D}/${systemd_unitdir}/system -- 2.7.4 -- _______________________________________________ meta-virtualization mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-virtualization
