<html>
    <head>
      <base href="https://bugs.freedesktop.org/" />
    </head>
    <body><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> changed
              <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED FIXED - systemd-resolved requires +x on resolved.conf parent directory"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=81015">bug 81015</a>
        <br>
             <table border="1" cellspacing="0" cellpadding="8">
          <tr>
            <th>What</th>
            <th>Removed</th>
            <th>Added</th>
          </tr>

         <tr>
           <td style="text-align:right;">Status</td>
           <td>NEW
           </td>
           <td>RESOLVED
           </td>
         </tr>

         <tr>
           <td style="text-align:right;">Resolution</td>
           <td>---
           </td>
           <td>FIXED
           </td>
         </tr></table>
      <p>
        <div>
            <b><a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED FIXED - systemd-resolved requires +x on resolved.conf parent directory"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=81015#c1">Comment # 1</a>
              on <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED FIXED - systemd-resolved requires +x on resolved.conf parent directory"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=81015">bug 81015</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>This was changed in
<a href="http://cgit.freedesktop.org/systemd/systemd/commit/?id=74b2466e14">http://cgit.freedesktop.org/systemd/systemd/commit/?id=74b2466e14</a>.
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.</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>