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

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Mar 3 13:13:05 PST 2015


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

--- Comment #2 from iTanguy <tanguy.person at gmail.com> ---
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.

-- 
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/839f9e14/attachment.html>


More information about the systemd-bugs mailing list