d78425eab4
This systemd service restarts Syncthing after resume from suspend via sending SIGHUP. By default Syncthing detects resume from sleep on its own by looking for jumps in the system clock. Since systemd knows exactly when the system resumes from sleep let's trigger the Syncthing restart from there. Doing this in systemd eliminates some annoying delay, as the service is restarted immediately after resume. Also, using the systemd dependency mechanism syncthing-inotify is restarted as well. $ journalctl -e --identifier syncthing --identifier syncthing-inotify --identifier systemd Feb 22 09:44:27 kronos systemd[1]: Reached target Sleep. Feb 22 09:44:27 kronos systemd[1]: Starting Suspend... Feb 22 09:44:33 kronos systemd[1]: Time has been changed Feb 22 09:44:33 kronos systemd[963]: Time has been changed Feb 22 09:44:33 kronos systemd[1]: Started Suspend. Feb 22 09:44:33 kronos systemd[1]: sleep.target: Unit not needed anymore. Stopping. Feb 22 09:44:33 kronos systemd[1]: Stopped target Sleep. Feb 22 09:44:33 kronos systemd[1]: Reached target Suspend. Feb 22 09:44:33 kronos systemd[1]: suspend.target: Unit is bound to inactive unit systemd-suspend.service. Stopping, too. Feb 22 09:44:33 kronos systemd[1]: Stopped target Suspend. Feb 22 09:44:33 kronos systemd[1]: Starting Restart Syncthing after resume... Feb 22 09:44:33 kronos syncthing[2561]: [35K66] OK: Exiting Feb 22 09:44:33 kronos systemd[1]: Started Restart Syncthing after resume. Feb 22 09:44:34 kronos systemd[963]: syncthing.service: Service hold-off time over, scheduling restart. Feb 22 09:44:34 kronos systemd[963]: Stopping Syncthing Inotify File Watcher... Feb 22 09:44:34 kronos systemd[963]: Stopped Syncthing Inotify File Watcher. Feb 22 09:44:34 kronos systemd[963]: Stopped Syncthing - Open Source Continuous File Synchronization. Feb 22 09:44:34 kronos systemd[963]: Started Syncthing - Open Source Continuous File Synchronization. Feb 22 09:44:34 kronos systemd[963]: Started Syncthing Inotify File Watcher. Feb 22 09:44:34 kronos syncthing[2836]: [35K66] INFO: syncthing v0.12.19 "Beryllium Bedbug" (go1.5.3 linux-amd64) builduser@svetlemodry 2016-02-14 19:26:33 UTC This system service has to be located in "/etc/systemd/system/syncthing-resume.service", and for packages in "/usr/lib/systemd/system/syncthing-resume.service". It can be enabled using "systemctl enable syncthing-resume.service".
Syncthing
This is the Syncthing project which pursues the following goals:
-
Define a protocol for synchronization of a folder between a number of collaborating devices. This protocol should be well defined, unambiguous, easily understood, free to use, efficient, secure and language neutral. This is called the Block Exchange Protocol.
-
Provide the reference implementation to demonstrate the usability of said protocol. This is the
syncthingutility. We hope that alternative, compatible implementations of the protocol will arise.
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.
Building
Building Syncthing from source is easy, and there's a guide. that describes it for both Unix and Windows systems.
Signed Releases
As of v0.10.15 and onwards, git tags and release binaries are GPG signed with the key D26E6ED000654A3E (see https://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
Please see the Syncthing documentation site.
All code is licensed under the MPLv2 License.