hostap/wpa_supplicant/systemd/wpa_supplicant.service.in

[Unit]
Description=WPA supplicant
Before=network.target
Wants=network.target

[Service]
Type=dbus
BusName=fi.epitest.hostap.WPASupplicant
ExecStart=@BINDIR@/wpa_supplicant -u

[Install]
WantedBy=multi-user.target
Alias=dbus-fi.epitest.hostap.WPASupplicant.service
wpa_supplicant: Add systemd support 2011-07-15 11:13:40 +02:00			`[Unit]`
			`Description=WPA supplicant`
systemd: Order wpa_supplicant before network.target Ordering the units before network.target causes them to be stopped after network.target on shutdown. This ensures that any network filesystems will be unmounted before wpa_supplicant is killed. Adding Wants=network.target ensures that network.target will be included in the active dependency graph. This is typical of units which are involved in networking setup functions. Signed-off-by: Mike Gilbert <floppym@gentoo.org> 2015-08-12 16:44:42 +02:00			`Before=network.target`
			`Wants=network.target`
wpa_supplicant: Add systemd support 2011-07-15 11:13:40 +02:00
			`[Service]`
			`Type=dbus`
			`BusName=fi.epitest.hostap.WPASupplicant`
wpa_supplicant: Edit BINDIR in dbus and systemd service files This is useful, since in Gentoo BINDIR=/usr/sbin. 2011-07-15 11:25:02 +02:00			`ExecStart=@BINDIR@/wpa_supplicant -u`
wpa_supplicant: Add systemd support 2011-07-15 11:13:40 +02:00
			`[Install]`
Use correct (multi-user) target when installing systemd units The 'network.target' is special (per systemd.special(7)), and is to be brought up indirectly when network is actually configured (i.e. through DHCP or static address settings). Irrelevant of that, all services should be always installed in multi-user.target. [Bug 427] 2011-12-29 20:39:34 +01:00			`WantedBy=multi-user.target`
wpa_supplicant: Add systemd support 2011-07-15 11:13:40 +02:00			`Alias=dbus-fi.epitest.hostap.WPASupplicant.service`