tags 749272 - wontfix severity 749272 serious retitle 749272 varnish doesn't source /etc/default/varnish when started but uses it when reloaded
Hello, Keeping file /etc/default/varnish when Varnish doesn't source it is confusing for users. And the worst is that the script /usr/share/varnish/reload-vcl (used by ExecReload in systemd unit) sources /etc/default/varnish ! Then users need to configure Varnish options in /etc/default/varnish *and* in varnish.service... and keep synchronized. The result is often a production failure when "systemctl reload varnish" then I consider this bug as serious severity (and it should be fixed for Stretch). There could be two bug fixes : - Using patch in this bug report to source /etc/default/varnish in varnish.service (and removing useless variables like START=yes) - Rewriting the script reload-vcl to not use /etc/default/varnish (and removing the file /etc/default/varnish) Regards, -- Grégory Colpart <r...@evolix.fr> GnuPG:4096R/B8612B5D Evolix - Hébergement et Infogérance Open Source http://www.evolix.fr/