Fix avaihi daemon start error

From: Kai Kang <[email protected]>

It shows error message which causes oe-selftest case parselogs fails:

Aug 29 13:50:23 qemux86 avahi-daemon[151]: ../../avahi-0.7/avahi-daemon/chroot.c: open() failed: No such file or directory
Aug 29 13:50:23 qemux86 avahi-daemon[148]: Failed to open /etc/resolv.conf: Invalid argument

Kai Kang (1):
avahi: launch avahi-daemon after connman

 .../files/0001-Fix-opening-etc-resolv.conf-error.patch     | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

--
2.20.0

From: Kai Kang <[email protected]>

When connman installed to image, /etc/resolv.conf is link to /etc/resolv-conf.connman. So launch avahi-daemon after connman too just same as after systemd-resolved.service.

---
 .../files/0001-Fix-opening-etc-resolv.conf-error.patch     | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

index 11e7e8a9bc..cb8b83fd23 100644
@@ -19,6 +19,11 @@ is marked as OE specific.
 Upstream-Status: Inappropriate [OE Specific]
 
 Signed-off-by: Chen Qi <[email protected]>
+
+When connman installed to image, /etc/resolv.conf is link to
+/etc/resolv-conf.connman. So launch avahi-daemon after connman too.
+
+Signed-off-by: Kai Kang <[email protected]>
 ---
  avahi-daemon/avahi-daemon.service.in | 1 +
  1 file changed, 1 insertion(+)

@@ -31,7 +36,7 @@ index 548c834..63e28e4 100644
  [Unit]
  Description=Avahi mDNS/DNS-SD Stack
  Requires=avahi-daemon.socket
-+After=systemd-resolved.service
++After=systemd-resolved.service connman.service
  
  [Service]
  Type=dbus

2.20.0