Hi all, Systemd offers an interesting feature that is Overriding vendor settings[1]. This consists of creating a file called /etc/systemd/system/MYSERVICE.service.d/ALEATORY.conf which will only include the bits one wants on top of the vendor settings (making upgrades of package relatively easy while keeping the overridden bits intact).
Taking MySQL for example one could : * Specify the ExecStart to contain --wsrep-new-cluster to start a Galera cluster * Change file limits specifying LimitNOFILE * Change the TimeoutSec value to timeout sooner * etc... With some major Linux OSes moving to systemd I do think this would be a nice to have feature. I tend to think that if the community agrees with the aforementioned feature it belongs to the systemd provider at the resource level. Else it would need to be implemented at the module level. If so, should we try to define a pattern that people can use in their module, so modules users can have a consistent way of doing it ? To summarize in two questions : * Do you think Overriding vendor settings feature from systemd should be handled via Puppet ? * If yes, do you think it belongs to the resource level of the module level ? Thank you all and have a great week end, [1] http://www.freedesktop.org/software/systemd/man/systemd.unit.html -- Yanis Guenane -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/6dbc82a0-c327-48ab-b246-38c6d86e8b56%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
