[systemd-devel] dhcpd (via systemd) @boottime which does not wait for the interface..

[Lennart Poettering]

On Wed, 04.05.16 13:09, lejeczek (peljasz at yahoo.co.uk) wrote:

> hi devels
> 
> I have my dhcpd to serve nothing but virbr0 (libvirt), OS is Centos 7.2
> Dhcpd would not start, complaining like this:
> 
> No subnet declaration for virbr0 (no IPv4 addresses).
> ** Ignoring requests on virbr0.  If this is not what
>    you want, please write a subnet declaration
>    in your dhcpd.conf file for the network segment
>    to which interface virbr0 is attached. **
> 
> and systemctl -l shows:
> ...
> systemd[1]: start request repeated too quickly for dhcpd.service
> ...
> 
> but suffices to restart dhcpd and all works!
> I've ##SELECTION_END##customized systemd's service conf, I've put:
> 
> After=libvirtd.service
> Requisite=libvirtd.service
> 
> but this did not help.
> Would you share your thoughts?
> many thanks.
> L.

Well, this is really a question to ask the libvirt folks. It really
depends on when libvirt creats that interface.

Alternatively you can also pull in the service from a udev rule (use
SYSTEMD_WANTS), to run it as soon as the interface shows up.

Lennart

-- 
Lennart Poettering, Red Hat