lokinet/debian/lokinet-router.lokinet-router.service
Jason Rhinelander 2e50981408 Use systemd service capabilities instead of setcap
Setcap causes problems (like issue #1007), so stop using it (and undo
the permission override on upgrade) and instead set capabilities via the
systemd services.

(This also fixes some AssertFileNotEmpty declarations that were in the
wrong places).
2020-01-14 18:52:04 -04:00

20 lines
553 B
Desktop File

[Unit]
Description=LokiNET: Anonymous Network layer thingydoo, router
AssertFileNotEmpty=/var/lib/lokinet/bootstrap.signed
Wants=network-online.target
After=network-online.target
[Service]
User=_lokinet
SyslogIdentifier=lokinet-router
WorkingDirectory=/var/lib/lokinet/router
CapabilityBoundingSet=CAP_NET_ADMIN CAP_NET_BIND_SERVICE
AmbientCapabilities=CAP_NET_ADMIN CAP_NET_BIND_SERVICE
ExecStart=/usr/bin/lokinet /var/lib/lokinet/router/lokinet.ini
Environment=LOKINET_NETID=lokinet
Restart=always
RestartSec=5s
[Install]
WantedBy=multi-user.target