I'm trying out the new foobar.service.d way of overriding unit files.
I thought that I'd be able to have a number of service instances that
were overridden differently but that does not seem to be the case (or,
at least, I can't get it to work).
I first updated to systemd 200 and tried foobar.service.d with
foobar.service.d/custom.conf; this works as described on the man page
and release notes.
I've also tried:
foobar@.service and foobar@.service.d/myinstance.conf
foobar@.service and foobar@myinstance.service.d/myinstance.conf
which don't work so I guess this isn't implemented. If so, would
something like that be a reasonable request to be considered ?
I was thinking...
foobar@.service
foobar@.service.d/myfirstinstance.conf
foobar@.service.d/mysecondinstance.conf
where the relevant .conf would be selected based on the instance name.
I was also wondering why the need for a separate sub-directory when
there's only one file inside it. Could a file like "foobar.service.conf"
be considered as an alternative (and, perhaps,
foo...@myinstance.service.conf) ?
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
