I disagree with this approach. A given daemon will have command line options that are imperative for proper operation as a daemon, and it will have command line options for behavior of the service once daemonized. If you have to invoke the daemon with ie `--daemonize` then it makes sense to have that "hardcoded" in ExecStart. If the options affect runtime behavior but can be changed without breaking the way the service is instantiated, they should be declared in an environment file. The cited github issue is going in the wrong direction, this kind of thing is what EnvironmentFile is for. I am very skeptical that upstream systemd discourages the use of EnvironmentFile in this way... Please take a look at https://src.fedoraproject.org/rpms/varnish/blob/master/f/varnish.service and https://src.fedoraproject.org/rpms/varnish/blob/master/f/varnish.params for some guidance on using EnvironmentFile for this use case. I really do not like the idea of overriding packaged configuration files to ie change the listening or allocate more memory ( read: routine administration of the software ).
-- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
