On 03/06/2013 00:33, Simon McVittie wrote: > [...] > The current upstream systemd has an "include" mechanism by which the > unit in /etc can say "copy all keys from the upstream version in /lib, > then set Foo=bar", and also a mechanism by which individual keys in a > unit can be overridden by a separate file in a .d directory > corresponding to that unit. I think the older version currently in > Debian has the former, but not the latter. > > I don't know about Upstart. If it doesn't have an equivalent of that > systemd feature, I'm sure one could be added. If it's just overriding statements in an init script, a .override file can be dumped into /etc/init. From init(5): > · Files ending in .override are called override files. If an override file > is present, the stanzas it contains take precedence over those > equivalently named stanzas in the corresponding configuration file > contents for a particular job. The main use for override files is to > modify how a job will run without having to modify its configuration file > directly. See the section Override File Handling below for further > details. -- Kind regards, Loong Jin
Attachment:
signature.asc
Description: OpenPGP digital signature