syncthing/etc/linux-systemd/system/syncthing@.service

[Unit]
Description=Syncthing - Open Source Continuous File Synchronization for %I
Documentation=http://docs.syncthing.net/
After=network.target
Wants=syncthing-inotify@.service

[Service]
User=%i
Environment=STNORESTART=yes
ExecStart=/usr/bin/syncthing -no-browser -logflags=0
Restart=on-failure
SuccessExitStatus=2 3 4
RestartForceExitStatus=3 4

[Install]
WantedBy=multi-user.target
systemd units for system/user 2014-11-19 08:42:05 +00:00			`[Unit]`
Some systemd tweaks - Removed environment file to keep the service file minimal. "systemctl edit syncthing.service" does the job if somebody wants to customize the service. - Changed "cmdline.target" to "default.target" as "cmdline.target" does not exist in systemd.special: http://www.freedesktop.org/software/systemd/man/systemd.special.html - Added a missing "After=network.target". - Added a documentation hint, thx @jaystrictor 2015-02-02 00:11:41 +00:00			`Description=Syncthing - Open Source Continuous File Synchronization for %I`
replaced (not all) wiki links to new location docs.syncthing.net 2015-06-03 17:08:58 +00:00			`Documentation=http://docs.syncthing.net/`
systemd units for system/user 2014-11-19 08:42:05 +00:00			`After=network.target`
Pull syncthing-inotify.service as an optional dep This patch adds syncthing-inotify.service as an optional dependency to syncthing.service. That means, if syncthing-inotify.service is available, it is started and stopped with syncthing. See discussion here: https://forum.syncthing.net/t/gnome-shell-extension-syncthing-icon/5759 2015-09-25 21:05:11 +00:00			`Wants=syncthing-inotify@.service`
systemd units for system/user 2014-11-19 08:42:05 +00:00
			`[Service]`
			`User=%i`
			`Environment=STNORESTART=yes`
systemd: Set -logflags to 0, provide -no-browser flag Syncthing should not try to start a browser when invoked by systemd. Furthermore we do not need any timestamps in the journal as systemd already handles this for us. 2015-03-21 19:46:14 +00:00			`ExecStart=/usr/bin/syncthing -no-browser -logflags=0`
on-failure instead of always as we cannot otherwise kill the service 2014-11-19 08:46:14 +00:00			`Restart=on-failure`
systemd: Fix error code definitions to prevent failed units The systemd exit code definitions (introduced in c586a17, refs #1324) caused problems. Per default systemd considers a return code != 0 as failed. So when you click on "Restart" in the WebUI an error appears: systemd[953]: syncthing.service: main process exited, code=exited, status=3/NOTIMPLEMENTED systemd[953]: Unit syncthing.service entered failed state. systemd[953]: syncthing.service failed. systemd[953]: syncthing.service holdoff time over, scheduling restart. systemd[953]: Started Syncthing - Open Source Continuous File Synchronization. systemd[953]: Starting Syncthing - Open Source Continuous File Synchronization... syncthing[13222]: [LFKUK] INFO: syncthing v0.10.30 (go1.4.2 linux-amd64 default) builduser@jara 2015-03-29 07:46:44 UTC To fix this error we have to add the "succes codes" 2, 3, 4 to "SuccessExitStatus": syncthing[13006]: [LFKUK] INFO: Restarting syncthing[13006]: [LFKUK] OK: Exiting systemd[953]: syncthing.service holdoff time over, scheduling restart. systemd[953]: Started Syncthing - Open Source Continuous File Synchronization. systemd[953]: Starting Syncthing - Open Source Continuous File Synchronization... syncthing[13031]: [LFKUK] INFO: syncthing v0.10.30 (go1.4.2 linux-amd64 default) builduser@jara 2015-03-29 07:46:44 UTC To make sure that syncthing restarts in case of error, and to make sure that "Restart=on-failure" actually works, let's remove "RestartPreventExitStatus=1". Systemd considers this as an error per default and the restart will be triggered successfully. 2015-03-29 22:45:55 +00:00			`SuccessExitStatus=2 3 4`
Added exit code definitions to systemd service files (fixes #1324) 2015-02-01 22:55:54 +00:00			`RestartForceExitStatus=3 4`
systemd units for system/user 2014-11-19 08:42:05 +00:00
			`[Install]`
			`WantedBy=multi-user.target`