[meta-virtualization] [meta-cloud-services] [PATCH 2/2] consul: Not automatically start system service on boot

[Bruce Ashfield]

merged

Bruce

On Mon, Sep 9, 2019 at 5:42 AM <zhe.he at windriver.com> wrote:
>
> From: He Zhe <zhe.he at windriver.com>
>
> 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 <zhe.he at windriver.com>
> ---
>  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
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II