[Pkg-varnish-devel] Bug#749272: varnish doesn't source /etc/default/varnish when started with systemd
Stig Sandbeck Mathisen
ssm at debian.org
Wed Mar 1 20:04:53 UTC 2017
Michael Stapelberg <stapelberg at 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.
Oh, and "ick!", but thanks. :)
I'd really like to avoid keeping /etc/default/* around for new installs.
--
Stig Sandbeck Mathisen
https://fnord.no/
More information about the Pkg-varnish-devel
mailing list