From a0ab850ec0f4608764e91e7a85e61a5a796cd9d4 Mon Sep 17 00:00:00 2001 From: Axel Kittenberger Date: Thu, 5 Jan 2017 19:18:23 +0100 Subject: [PATCH] readme --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index bae4b11..2361daf 100644 --- a/README.md +++ b/README.md @@ -8,6 +8,8 @@ Rsync+ssh is an advanced action configuration that uses a SSH to act file and di Fine-grained customization can be achieved through the config file. Custom action configs can even be written from scratch in cascading layers ranging from shell scripts to code written in the [Lua language](http://www.lua.org/). This way simple, powerful and flexible configurations can be acheived. See [the manual](https://axkibe.github.io/lsyncd/) for details. +Lsyncd 2.2.1 requires rsync >= 3.1 on all source and target machines. + License: [GPLv2](http://www.fsf.org/licensing/licenses/info/GPLv2.html) or any later GPL version. When to use @@ -20,6 +22,8 @@ Other synchronization tools [GlusterFS](http://www.gluster.org) and [BindFS](http://bindfs.org/) use a FUSE-Filesystem to interject kernel/userspace filesystem events. +[Mirror](https://github.com/stephenh/mirror) is an asynchronous synchronisation tool that takes use of the inotify notifications much like Lsyncd. The main differences are: it is developed specifically for master-master use, thus running on a daemon on both systems, uses its own transportation layer instead of rsync and is Java instead of Lsyncd's C core with Lua scripting. + Lsyncd usage examples --------------------- ```lsyncd -rsync /home remotehost.org::share/```