diff options
| author | Chen Qi <Qi.Chen@windriver.com> | 2018-06-21 14:00:23 +0800 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2018-06-27 13:53:28 +0100 |
| commit | 647db1d9eb65b225ffbb6953f796232026bfa935 (patch) | |
| tree | 6b9bcc7daeed5d895cfb6f0e3ed4b2d9ed0960bd /scripts/lib/checklayer/context.py | |
| parent | 75529d384bfeaf52befccb892cf41f22dc02668b (diff) | |
| download | openembedded-core-647db1d9eb65b225ffbb6953f796232026bfa935.tar.gz openembedded-core-647db1d9eb65b225ffbb6953f796232026bfa935.tar.bz2 openembedded-core-647db1d9eb65b225ffbb6953f796232026bfa935.zip | |
avahi: fix error at boot time for avahi-daemon.service
The following error messages appear now and then at boot time.
avahi-daemon/chroot.c: open() failed: No such file or directory
Failed to open /etc/resolv.conf: Invalid argument
The problem is about /etc/resolv.conf. In Yocto's systemd based
systems, it's a symlink to /etc/resolv-conf.systemd which in turn
is a symlink to /run/systemd/resolve/resolv.conf. The systemd-resolved
service handles creation of /run/systemd/resolve/resolv.conf file.
So if avahi-daemon is started before systemd-resolved, the error messages
appear.
Fix this problem by making avahi-daemon start after systemd-resolved.
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'scripts/lib/checklayer/context.py')
0 files changed, 0 insertions, 0 deletions