<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Empty conf.d directories are not created, for configuration files that support it"
href="https://bugs.freedesktop.org/show_bug.cgi?id=89397#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Empty conf.d directories are not created, for configuration files that support it"
href="https://bugs.freedesktop.org/show_bug.cgi?id=89397">bug 89397</a>
from <span class="vcard"><a class="email" href="mailto:zbyszek@in.waw.pl" title="Zbigniew Jedrzejewski-Szmek <zbyszek@in.waw.pl>"> <span class="fn">Zbigniew Jedrzejewski-Szmek</span></a>
</span></b>
<pre>(In reply to iTanguy from <a href="show_bug.cgi?id=89397#c2">comment #2</a>)
<span class="quote">> 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.</span >
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.
<span class="quote">> 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.</span >
I'll update the comment to deemphasize those directories.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>