[systemd-devel] Per-instance override with foobar.service.d

[John Lane]

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 at .service and foobar at .service.d/myinstance.conf
foobar at .service and foobar at 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 at .service
foobar at .service.d/myfirstinstance.conf
foobar at .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, 
foobar at myinstance.service.conf) ?