On 17/07/14 18:57, Sam Varshavchik wrote:
Dhcpd on my server has suddenly started taking to start before the IP address (statically assigned) has been configured on the network interface and consequently bombs out. The systemd service for dhcpd has
After=network.target
should this be network-online.target?
Won't make a difference.
Welcome to the systemd fan club.
Install the following file as /etc/systemd/system/wait-for-network.service
Thanks Sam, actually it did seem to work fine for me. I changed it to network-online.target and dhcpd did start on boot. I'm using the traditional 'network' service rather than NetworkManager because at the time NetworkManager didn't support bridges, so I'm not sure if that differs from your setup. I did however have to jump through similar hoops with autofs though on my client, eventually making the display manager depend on NetworkManager-wait-online.service because it was possible to login before autofs even started. It seems that Bind might have issues along similar lines to dhcpd too, except that it does start but refused to serve DNS requests until I restart the service.