Stig Sandbeck Mathisen <s...@debian.org> writes: > Michael Stapelberg <stapelb...@debian.org> writes: > >> Yet another alternative might be (and it pains me to say that, but >> maybe it’s required to not break people’s setups) to have the service >> file start a wrapper shell script which evaluates >> /etc/default/varnish before starting varnish. > > That could actually be done when upgrading the package from whatever > is in stable currently. > > For instance: If upgrading from 4.0.2-1, add a > /etc/systemd/system/varnish.service.d/upgrade.conf with such a shell > wrapper for people upgrading from the version in current stable.
Hm, after bootstrapping a stable debian installation, it looks like the varnish systemd unit on stable didn't use an environment file at all. It did, however, have ExecReload= set, using the reload-vcl script which I'm not very content with. Therefore, I think this issue can be resolved with just removing "ExecReload=/usr/share/varnish/reload-vcl" from the systemd unit again, and not have a "reload" action at all. This has also been discussed previously at https://github.com/varnishcache/pkg-varnish-cache/issues/30 for the upstream packaging. -- Stig Sandbeck Mathisen https://fnord.no/
