[systemd-devel] Per-instance override with foobar.service.d
Zbigniew Jędrzejewski-Szmek
zbyszek at in.waw.pl
Fri Apr 12 06:00:53 PDT 2013
> > foobar at .service and foobar at .service.d/myinstance.conf
> > foobar at .service and foobar at myinstance.service.d/myinstance.conf
This would be possible, if somebody implements it.
> > 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
The idea is that different sources (rpms, administrator, whatever)
provide snippets that are then merged. So there's no central "registration"
of snippet names, and the namespace cannot be reused for instances.
> > 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)
There can be multiple files.
Zbyszek
More information about the systemd-devel
mailing list