<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jun 30, 2017 at 10:56 AM, Michael Biebl <span dir="ltr"><<a href="mailto:biebl@debian.org" target="_blank">biebl@debian.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">Am 30.06.2017 um 16:42 schrieb Laurent Bigonville:<br>
> Package: systemd<br>
> Version: 233-9<br>
> Severity: normal<br>
><br>
> Hi,<br>
><br>
> When doing "$ systemd-resolve <a href="http://example.com" rel="noreferrer" target="_blank">example.com</a>", I get the following error:<br>
><br>
> <a href="http://example.com" rel="noreferrer" target="_blank">example.com</a>: resolve call failed: Unit dbus-org.freedesktop.resolve1.<wbr>service not found.<br>
><br>
> Shouldn't resolved be automatically activated?<br>
<br>
</span>I think that's by design. systemd-resolve should not autostart resolved<br>
if it's not enabled. At least I would be unhappy if it did so.<br></blockquote><div><br></div><div>While systemd-resolve activating resolved sounds sort of reasonable, dbus-activating resolved would mean nss-resolve would start resolved if not running... which I think is not cool. </div></div><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><br>Saludos,<br>Felipe Sateler</div>
</div></div>