<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <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#c2">Comment # 2</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 <a class="email" href="mailto:tanguy.person@gmail.com" title="iTanguy <tanguy.person@gmail.com>"> iTanguy</a> <pre>IMHO, it would promote further the use of the .d/ dropins. 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. 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. In fact, not having these folders by default could block users. Or at least it's happened to me : I was hesitating between a documentation/comment bug, or a feature not finished, or a feature not enabled in my distribution (ArchLinux)... More pragmaticaly : - I don't know which rights, user and group I should set to these folders, for it to work, but also to be secure. - ArchLinux package build system can't create empty folders unless they are created by the upstream project.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>