[OE-core] [PATCH 1/2] systemd: enable resolved and networkd

Maxin B. John maxin.john at intel.com
Fri Jul 7 08:10:43 UTC 2017


Hi Patrick,

On Thu, Jul 06, 2017 at 05:12:05PM +0200, Patrick Ohly wrote:
> On Mon, 2017-06-12 at 18:10 +0300, Maxin B. John wrote:
> > Enable systemd-resolved and systemd-networkd by default.
> > Make it co-exist with connman and  Fix associated problems
> > in read-only rootfs.
> > 
> > Fixes [YOCTO #11331]
> 
> Let me come back to this, because I think it is not quite working as
> intended yet.
> 
> The goal is that the "right" resolver is chosen via alternative
> priorities, right? So during build time, we set /etc/resolv.conf to what
> is the desired resolver.

Yes. Eventhough for practical reasons, ConnMan's resolver is preferred when
we use ConnMan in the image. That is the reason why we have
"Conflicts=systemd-resolved.service" in "connman.service.in"

> However, there's still a L+ entry for /etc/resolv.conf
> in /usr/lib/tmpfiles.d/connman_resolvconf.conf:
> 
> L+	/etc/resolv.conf	- - - -	/var/run/connman/resolv.conf
> As a result, when systemd is used and the rootfs is read/write, then
> systemd overwrites /etc/resolv.conf, leading to:
> 
> # ls -l /etc/resolv.conf 
> lrwxrwxrwx    1 root     root            28 Jul  6 14:44 /etc/resolv.conf -> /var/run/connman/resolv.conf
> 
> That happens even if systemd-resolved has a higher priority and should
> be used.
> 
> Maxin, do you agree? Can you finish this work and patch the ConnMan
> recipe so that it behaves as expected?

Looks reasonable to me. Thanks for suggesting this. Will update the recipe.

> -- 
> Best Regards, Patrick Ohly

Best Regards,
Maxin



More information about the Openembedded-core mailing list