| Summary: | systemd's resolved conflicts with connman | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Ross Burton <ross.burton> |
| Component: | connectivity | Assignee: | Chen Qi <Qi.Chen> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | meta.mr.watcher, meta.watcher, net147 |
| Version: | 1.7 | ||
| Target Milestone: | 2.3 M4 | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Ross Burton
2014-09-09 09:45:08 UTC
Note that there's a patch due to be merged to disable resolved/networkd, so you'll need to re-enable them before testing. Patch to disable resolved and networkd integrated: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=ecb4014c58bfcffc0ace20db338bced54775b815 . Reassigning to Chen as he's the systemd maintainer. Currently in oe-core we've "solved" this by disabling networkd and resolved in systemd. This clearly isn't optimal, especially for situations where networkd is preferable to connmand (such as containers or servers). We need to make networkd and resolved work when they are enabled if connmand isn't also installed, and somehow ensure that they're mutually exclusive. I just did some tests. 1) systemd + resolved 2) systemd + connman 3) systemd + resolved + connman In the above three cases, I didn't see any problem. I'm going to close this bug if there's no objection. Regards, Chen Qi Close this bug as stated in the above comment. |