[systemd-bugs] [Bug 81015] systemd-resolved requires +x on resolved.conf parent directory

[bugzilla-daemon at freedesktop.org]

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

Zbigniew Jedrzejewski-Szmek <zbyszek at in.waw.pl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #1 from Zbigniew Jedrzejewski-Szmek <zbyszek at in.waw.pl> ---
This was changed in
http://cgit.freedesktop.org/systemd/systemd/commit/?id=74b2466e14.
systemd-resolved will now loudly complain, but continue.

But in general, for most daemons it makes sense to fail to start if their
configuration files are mangled or otherwise broken, as this means that there's
a problem that needs to be fixed, and often it is better to abort then delived
half-broken results, so this change might get reverted.

Also, systemd-resolved simply tries to open the file using a direct open()
call. If the kernel does not allow that, then the daemon cannot do anything
about it.

-- 
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/20140717/0ad6f657/attachment.html>