Require network-online insetad of network target

Depending on the network-online.target rather than network.target
will result in more reliable service startups since network.target
does not indicate that the network stack has fully started, only
that networking has been initialized. When starting network-related
services like neturon, where a bridge or veth interface may be
expected to exist already, relying on network.target can cause broken
service startup during system reboots since the interfaces depended
on may not exist yet once network.target is reached.

By relying on network-online.target instead, units will start more
reliably during system reboots or network restarts.

The systemd docs at
https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/#conceptsinsystemd
provide more information about why we should use the network-online
instead of the network target.

Change-Id: I7fca0af11bf7a0fed18294c97b81ef1dfa074e34
This commit is contained in:
Logan V 2019-05-03 10:13:44 -06:00
parent 2b141286d0
commit 9fd965fc1b

View File

@ -72,7 +72,7 @@ systemd_PrivateNetworkLocalDHCPGateway: "10.0.5.1/24"
# the "systemd_services" dictionary option "after_targets".
systemd_after_targets:
- syslog.target
- network.target
- network-online.target
# List of documentation information that will be presented in the unit. This
# option is a list of documentation items which can be local or online.