[CCing the bug report] Am 10.10.2018 um 01:33 schrieb Michael Pietsch: > Thanks this solved the problem. I literally searched for hours but not > once stumbled about the need to use systemd-networkd-wait-online because > I thought it was about the link-local address and not the > systemd-networkd itself.
I think the wiki page I referenced explains it rather well. But improvements to the documentation are always welcome. > From a user perspective it might help if the man page would explicitly > say that the network might not be fully configured after this service is > started and you have to use systemd-networkd-wait-online.service. > > Greeting another Michael :D > > Am 10.10.2018 um 0:44 schrieb Michael Biebl: >> Am 09.10.18 um 23:33 schrieb mich...@mi-pietsch.de: >> >>> The service file is >>> ``` >>> [Unit] >>> Description=BIND Domain Name Server >>> Documentation=man:named(8) >>> After=network.target systemd-networkd.service network-online.target >>> Wants=systemd-networkd.service network-online.target network.target >> Please drop >> Wants/After=systemd-networkd.service >> You don't want a dependency on a specific network configuration in your >> unit files. >> >> What you need is to actually make network-online.target delay until the >> network is configured. >> You thus most likely want to use >> systemctl enable systemd-networkd-wait-online.service >> >> network-online.target by itself does nothing. It needs services which >> hook into network-online.target and delay the target until network is >> configured. >> >> Michael >> >> -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
