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

Patrick Ohly patrick.ohly at intel.com
Thu Jul 6 15:12:05 UTC 2017


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.

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?

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.






More information about the Openembedded-core mailing list