FS#55862 - dhcpd4 cannot run as
Attached to Project:
Arch Linux
Opened by Christian Wolf (christianlupus) - Wednesday, 04 October 2017, 13:35 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 08 October 2017, 16:10 GMT
Opened by Christian Wolf (christianlupus) - Wednesday, 04 October 2017, 13:35 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 08 October 2017, 16:10 GMT
|
Details
The dhcp daemon checks on start-up for the relevant
interfaces to run on. I have a arch machine that seems to
have problems when starting the dhcpd4.service at system
start. The daemon cannot find any matching link and refuses
to run. Thus the system gets in degraded state.
The systemd config file denotes the dhcpd4 to be started with After=network.target In my opinion this is wrong as the network needs to be already up and an ip must be assigned. So it should be network-online.target instead. Then the user should enable the corresponding X-wait-online.service (e.g. systemd-networkd-wait-online.service). Then the dhcpd4 will start as desired. Additional info: dhcp version 4.3.5-2 |
This task depends upon
Closed by Doug Newgard (Scimmia)
Sunday, 08 October 2017, 16:10 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#52557
Sunday, 08 October 2017, 16:10 GMT
Reason for closing: Duplicate
Additional comments about closing:
Comment by
Christian Wolf (christianlupus) -
Wednesday, 04 October 2017, 14:59 GMT
I tried it with a virtual machine just now and it seems not to be
reproducable in the sense that the dhcp daemon gets started
correctly. So it seems to depend on other configurations of the
system and in which order systemd loads the services.