In the interest of backwards compatibility this needs to look something like
Environment=KRB5_KTNAME=/etc/libvirt/libvirt.keytab EnvironmentFile=/etc/default/libvirt-bin ExecStart=/usr/sbin/libvirtd $LIBVIRTD_ARGS (Assuming that LIBVIRTD_ARGS is specified in the default/ file). Indeed this style is obsolete as a lot of packages implement that in a totally different way. The better approach is to use a configuration file that is actually read by libvirt itself, instead of passing configuration on the command line. This of course needs to be supported upstream, but at least then it will work the same way everywhere and doesn't need to be documented (differently) by distros working around the lack of a proper config file. As a fallback, one can create a drop-in which overrides/adds particular keys to the .service file, with "systemctl edit libvirt-bin", which is a convenience shortcut for creating a /etc/systemd/system/libvirt- bin.service.d/mysettings.conf . It's also conceivable to do that in the postinst during package upgrade. ** Summary changed: - Systemd Libvirt-bin script broken + libvirt-bin.service does not read /etc/default/libvirt-bin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1541810 Title: libvirt-bin.service does not read /etc/default/libvirt-bin To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/1541810/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
