blob: 11e7e8a9bc7865afafbad2b7f6d0549fda81b2f0 [file] [log] [blame]
Brad Bishop1a4b7ee2018-12-16 17:11:34 -08001From 78967814f5c37ed67f4cf64d70c9f76a03ee89bc Mon Sep 17 00:00:00 2001
2From: Chen Qi <Qi.Chen@windriver.com>
3Date: Wed, 20 Jun 2018 13:57:35 +0800
4Subject: [PATCH] Fix opening /etc/resolv.conf error
5
6Fix to start avahi-daemon after systemd-resolved.service. This is because
7/etc/resolv.conf is a link to /etc/resolv-conf.systemd which in turn is
8a symlink to /run/systemd/resolve/resolv.conf. And /run/systemd/resolve/resolv.conf
9is created by systemd-resolved.service by default in current OE's systemd
10based systems.
11
12This fixes errro like below.
13
14 Failed to open /etc/resolv.conf: Invalid argument
15
16In fact, handling of /etc/resolv.conf is quite distro specific. So this patch
17is marked as OE specific.
18
19Upstream-Status: Inappropriate [OE Specific]
20
21Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
22---
23 avahi-daemon/avahi-daemon.service.in | 1 +
24 1 file changed, 1 insertion(+)
25
26diff --git a/avahi-daemon/avahi-daemon.service.in b/avahi-daemon/avahi-daemon.service.in
27index 548c834..63e28e4 100644
28--- a/avahi-daemon/avahi-daemon.service.in
29+++ b/avahi-daemon/avahi-daemon.service.in
30@@ -18,6 +18,7 @@
31 [Unit]
32 Description=Avahi mDNS/DNS-SD Stack
33 Requires=avahi-daemon.socket
34+After=systemd-resolved.service
35
36 [Service]
37 Type=dbus
38--
392.11.0
40