On Sat, 8 Dec 2012, Curtis Shimamoto wrote:
On 12/09/12 at 04:01am, Dimitrios Apostolou wrote:
Imagine that in /usr unit file the daemon is being called as "binary
-d". So I create the /etc unit file that supersedes it and calls it
as "blah -d -n1". Then the package gets updated and the /usr unit
file changes to "binary -d --lock=/whatever/path".
As you can see I won't get the update because I've overriden the
unit file, I won't get any warning either, but if the original unit
file called "binary -d --lock=/whatever/path $BLAH_ARGS" there would
have been no such problem.
Keep some kind of configuration fine and use the .include feature of
systemd units to source the config with EnvironmentFile=.
Hi Curtis, I can't see how the .include directive would help in the case I
mentioned. But even in other cases that it helps, I think it's a much more
heavyweight solution to the problem, than the /etc/conf.d EnvironmentFile.
What do you think?
Dimitris
