abraunegg-onedrive/contrib/systemd/onedrive.service.in

[Unit]
Description=OneDrive Free Client
Documentation=https://github.com/abraunegg/onedrive
After=network-online.target
Wants=network-online.target

[Service]
# Commented out hardenings are disabled because they may not work out of the box on your distribution
# If you know what you are doing please try to enable them.

ProtectSystem=full
PrivateUsers=true
#PrivateDevices=true
ProtectHostname=true
#ProtectClock=true
ProtectKernelTunables=true
#ProtectKernelModules=true
#ProtectKernelLogs=true
ProtectControlGroups=true
RestrictRealtime=true
ExecStart=@prefix@/bin/onedrive --monitor
Restart=on-failure
RestartSec=3
RestartPreventExitStatus=3

[Install]
WantedBy=default.target
capability to run as service 2015-11-29 21:12:44 +01:00			`[Unit]`
			`Description=OneDrive Free Client`
update unit files documentation link (#126) * update unit files documentation link 2018-08-17 00:02:56 +02:00			`Documentation=https://github.com/abraunegg/onedrive`
Update systemd service files * Update single user file so that it requries the network to be online before the service starts * Create a multi-user service file for multi-user environments with each user having their own onedrive account configuration (#321) - file provided by @sbocquet 2018-04-12 04:43:23 +02:00			`After=network-online.target`
Update Makefile and systemd files * Change the ordering of 'make install' so that directories and permissions are set first * Use wildcard to copy service files to systemd directory as 'install' was failing when there was @ in the script * Update systemd units files based on https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ for starting the onedrive service 2018-04-22 00:29:43 +02:00			`Wants=network-online.target`
capability to run as service 2015-11-29 21:12:44 +01:00
			`[Service]`
systemd: disable non-working remaining sandboxing options (#2205) * systemd: use PrivateUsers= in user unit ProtectSystem= and other sandboxing options require a user namespace in order to work as user units (the user manager does not run as root and thus without a user namespace it is unable to perform mounts). 2022-11-09 21:15:11 +01:00			`# Commented out hardenings are disabled because they may not work out of the box on your distribution`
Add SystemD hardening (#1720) * Add SystemD hardening Co-authored-by: abraunegg <alex.braunegg@gmail.com> 2021-11-24 20:28:46 +01:00			`# If you know what you are doing please try to enable them.`
systemd: disable non-working remaining sandboxing options (#2205) * systemd: use PrivateUsers= in user unit ProtectSystem= and other sandboxing options require a user namespace in order to work as user units (the user manager does not run as root and thus without a user namespace it is unable to perform mounts). 2022-11-09 21:15:11 +01:00
Add SystemD hardening (#1720) * Add SystemD hardening Co-authored-by: abraunegg <alex.braunegg@gmail.com> 2021-11-24 20:28:46 +01:00			`ProtectSystem=full`
systemd: disable non-working remaining sandboxing options (#2205) * systemd: use PrivateUsers= in user unit ProtectSystem= and other sandboxing options require a user namespace in order to work as user units (the user manager does not run as root and thus without a user namespace it is unable to perform mounts). 2022-11-09 21:15:11 +01:00			`PrivateUsers=true`
Add SystemD hardening (#1720) * Add SystemD hardening Co-authored-by: abraunegg <alex.braunegg@gmail.com> 2021-11-24 20:28:46 +01:00			`#PrivateDevices=true`
			`ProtectHostname=true`
			`#ProtectClock=true`
			`ProtectKernelTunables=true`
			`#ProtectKernelModules=true`
			`#ProtectKernelLogs=true`
			`ProtectControlGroups=true`
			`RestrictRealtime=true`
autoconf based build system (#287) * Add autoconf based build system 2019-04-17 03:06:24 +02:00			`ExecStart=@prefix@/bin/onedrive --monitor`
Update systemd service files * Update single user file so that it requries the network to be online before the service starts * Create a multi-user service file for multi-user environments with each user having their own onedrive account configuration (#321) - file provided by @sbocquet 2018-04-12 04:43:23 +02:00			`Restart=on-failure`
			`RestartSec=3`
Change unauthorized-api exit code to 3 (Issue #567) (#572) * Changes unauthorized-api exit code to 3 * Systemd will not restart on exit code 3 2019-07-06 00:01:04 +02:00			`RestartPreventExitStatus=3`
capability to run as service 2015-11-29 21:12:44 +01:00
			`[Install]`
systemd: disable non-working remaining sandboxing options (#2205) * systemd: use PrivateUsers= in user unit ProtectSystem= and other sandboxing options require a user namespace in order to work as user units (the user manager does not run as root and thus without a user namespace it is unable to perform mounts). 2022-11-09 21:15:11 +01:00			`WantedBy=default.target`