core-agent-linux/vm-systemd/qubes-network.service

[Unit]
Description=Qubes network forwarding setup
ConditionPathExists=/var/run/qubes-service/qubes-network
Before=network.target
After=network-pre.target qubes-iptables.service

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/lib/qubes/init/network-proxy-setup.sh

[Install]
WantedBy=multi-user.target
vm/init: introduce SystemD startup scripts 2012-01-10 12:10:16 +01:00			`[Unit]`
			`Description=Qubes network forwarding setup`
			`ConditionPathExists=/var/run/qubes-service/qubes-network`
vm/systemd: fix qubes-network dependencies network.target isn't enabled by default... 2012-01-14 01:35:58 +01:00			`Before=network.target`
Order network management units after network-pre.target Network management software should order itself after network-pre.target (man 7 systemd.special) so that other units can order themselves before the beginning of network initialization. (qubes-misc-post too because it calls setup-ip.) Relevant for QubesOS/qubes-issues#2108 2016-06-30 17:41:14 +02:00			`After=network-pre.target qubes-iptables.service`
vm/init: introduce SystemD startup scripts 2012-01-10 12:10:16 +01:00
			`[Service]`
			`Type=oneshot`
			`RemainAfterExit=yes`
			`ExecStart=/usr/lib/qubes/init/network-proxy-setup.sh`

			`[Install]`
vm/systemd: fix qubes-network dependencies network.target isn't enabled by default... 2012-01-14 01:35:58 +01:00			`WantedBy=multi-user.target`