On Sun, Apr 30, 2017 at 10:10 AM, Pol Vangheluwe <[email protected]> wrote:
> Just want to report this small problem (without functional impact at first > sight). > The BLFS book says to simple “enable" the avahi-daemon systemd unit, but I > find this in the system logs: > > apr 30 14:49:12 ppc125 avahi-daemon[222]: *chroot.c: open() failed: No > such file or directory* > apr 30 14:49:12 ppc125 avahi-daemon[212]: *Failed to open > /etc/resolv.conf: Invalid argument* > > This is a symlink: > > lrwxrwxrwx 1 root root 32 10 okt 2015 /etc/resolv.conf -> > /run/systemd/resolve/resolv.conf > > Looks like the avahi-daemon is launched before the configuration file is > created by systemd-resolved. > There is maybe a need to add a systemd unit file for avahi, describing the > dependency to systemd-resolved? > > Remark: my system is LFS-7.7 and I followed BLFS-7.6, but the BLFS-8.0 > instructions are very similar, so I expect the same problem there. > > pvg > > Hello, Those are harmless and to be expected. I've had them on every single version of BLFS systemd that I've used (and as the maintainer, that's all of them). Avahi continues to work fine. It's actually an issue in glibc, but we're waiting for a new version of Avahi to fix this up. In the meantime, it should be fine. Thanks, Douglas R. Reno LFS/BLFS systemd maintainer
-- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
