[systemd-bugs] [Bug 89397] Empty conf.d directories are not created, for configuration files that support it

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=89397

--- Comment #3 from Zbigniew Jedrzejewski-Szmek <zbyszek at in.waw.pl> ---
(In reply to iTanguy from comment #2)
> The .d/ drop-ins add complexity to systemd, but it is part of systemd,
> already available, useful, and it remains an option. If it's too complex and
> adds confusion, maybe it should be improved. The goal of such a feature is
> that it e used as widely as possible.
Not in this case. /etc/systemd/logind.conf.d/*.conf is a mechanism for
packagers to provide configuration snippets without creating conflicts. The
administrator should simply modify /etc/systemd/logind.conf. The situation for
those configuration files is different than for unit files because by default
no configuration is required and there's no downside to using
/etc/systemd/logind.conf directly.

> They are already advocated in the comments of .conf files :
> # You can override the directives in this file by creating files in
> # /etc/systemd/logind.conf.d/*.conf.
I'll update the comment to deemphasize those directories.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20150303/c539b7bc/attachment.html>