dnscrypt-proxy/systemd/dnscrypt-proxy.service

[Unit]
Description=DNSCrypt client proxy
Documentation=man:dnscrypt-proxy(8)
Requires=dnscrypt-proxy.socket
After=network.target
Before=nss-lookup.target
Wants=nss-lookup.target

[Install]
Also=dnscrypt-proxy.socket
WantedBy=multi-user.target

[Service]
Type=simple
NonBlocking=true

# Change this
ExecStart=/opt/dnscrypt-proxy/dnscrypt-proxy
systemd support How does it work? I don't know. Does it work? I don't know. Would I encourage its use? No. 2018-01-24 14:44:32 +01:00			`[Unit]`
			`Description=DNSCrypt client proxy`
			`Documentation=man:dnscrypt-proxy(8)`
			`Requires=dnscrypt-proxy.socket`
			`After=network.target`
			`Before=nss-lookup.target`
Update systemd service to pull nss-lookup.target in. According to systemd.special(7), nss-lookup.target is a Special Passive System Unit. This means that services depending on its functionality should order themselves after the target with an After= type dependency, but should not have a Wants= dependency for them. Therefore, nss-lookup.target should be pulled in by the providing services instead, or the consumer services will never be able to order themselves after the providing services since nss-lookup.target would not be pulled in at any point in the boot process. dnscrypt-proxy.service provides name lookup functionality, and has a Before= dependency on nss-lookup.target. However, it should have a Wants= dependency on it as well in order to indicate readiness of name lookup functionality. 2018-02-02 15:51:38 +01:00			`Wants=nss-lookup.target`
systemd support How does it work? I don't know. Does it work? I don't know. Would I encourage its use? No. 2018-01-24 14:44:32 +01:00
			`[Install]`
			`Also=dnscrypt-proxy.socket`
			`WantedBy=multi-user.target`

			`[Service]`
			`Type=simple`
			`NonBlocking=true`

			`# Change this`
			`ExecStart=/opt/dnscrypt-proxy/dnscrypt-proxy`