da0b78c67a
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.
syncthing
This is the syncthing project. The following are the project goals:
-
Define a protocol for synchronization of a folder between a number of collaborating devices. The protocol should be well defined, unambiguous, easily understood, free to use, efficient, secure and language neutral. This is the Block Exchange Protocol.
-
Provide the reference implementation to demonstrate the usability of said protocol. This is the
syncthingutility. It is the hope that alternative, compatible implementations of the protocol will come to exist.
The two are evolving together; the protocol is not to be considered stable until syncthing 1.0 is released, at which point it is locked down for incompatible changes.
Getting Started
Take a look at the getting started guide.
There are a few examples for keeping syncthing running in the background on your system in the etc directory.
There is an IRC channel, #syncthing on Freenode, for talking directly
to developers and users (when awake and present, etc.).
Building
Building Syncthing from source is easy, and there's a guide. that describes it for both Unix and Windows.
Signed Releases
As of v0.10.15 and onwards, git tags and release binaries are GPG signed with the key D26E6ED000654A3E (see http://syncthing.net/security.html). For release binaries, MD5 and SHA1 checksums are calculated and signed, available in the md5sum.txt.asc and sha1sum.txt.asc files.
Documentation
The syncthing documentation is on the Github wiki.
All code is licensed under the MPLv2.