So, as noted, I disagree with Stig's assertions. I think it's better for the distribution to provide the service in a way that includes discoverable ways to adjust common commandline parameters. Varnish doesn't really give us a file like /etc/varnish.conf for things like listen port parameters so the sysconfig EnvironmentFile method gives us the next best thing. Your approach requires a deliberate override of the packaged service unit which could have potentially undesirable effects in the future. As a qualified and experienced RPM maintainer I do not understand your aversion to using EnvironmentFile for it's intended purpose, or your desire for a more troublesome user experience inherent to the alternative. We shouldn't need such dramatic and [subjectively] non-intuitive workarounds to effect routine configuration of your package.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573561 Title: /etc/default/varnish is ignored (fixed values in systemd service) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1573561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
