[systemd-devel] Prioritize the /etc configuration over /usr/lib also with .include

[Zbigniew Jędrzejewski-Szmek]

On Wed, Sep 17, 2014 at 08:52:00AM +0200, Pavel Raiskup wrote:
> On Wednesday 17 of September 2014 01:33:02 Zbigniew Jędrzejewski-Szmek wrote:
> > On Tue, Sep 16, 2014 at 05:07:06PM +0200, Pavel Raiskup wrote:
> > > > for example
> > > > tmpfiles.d/systemd.conf and tmpfiles.d/systemd-nologin.conf are split
> > > > exactly for the purpose of making it easier to override separately. The
> > > > case of unit files is slightly different, but we really want to have the
> > > > same semantics for all configuration file overrides in systemd.
> > > 
> > > Could you please be more specific?  You mean that the /usr/lib
> > > configuration should have bigger priority than /etc?
> >
> > There are two independent rules: one is that files with the same name
> > override each other (and /etc has higher priority than /usr/lib), and
> > second that dropins have higher priority than the "basic" configuration
> > files.
> >
> > So to answer your question directly: no, /usr/lib configuration
> > has lower priority, but it might still be visible if not override by
> > a file with the same name in /etc or /run.
> 
> Thanks, I agree, and yet another rule on top of that -- the /usr/lib
> dropins _are ignored_ if /etc service overriding the one in /usr/lib
> exists [1] which seems like it is expected (and I appreciate that
> behavior).
Sorry, but the .include mechanism is deprecated (and almost unused
nowadays) and we are not going to work on changing the semantics of
something that we don't want people to use anyway.

Zbyszek