Lsyncd (Live Syncing Daemon) synchronizes local directories with remote targets
Go to file
2018-06-19 09:06:18 +02:00
cmake from yokogawa-k on master, also find unversioned lua 2018-03-26 11:38:57 +02:00
core cleanups, bug fixing 2018-06-19 09:06:18 +02:00
default rewriting inheritance logic. splitting default and proto 2018-06-14 09:18:29 +02:00
doc/manpage reworking signal system 2018-06-04 08:54:06 +02:00
examples cleanups 2018-03-09 13:32:58 +01:00
mantle cleanups, bug fixing 2018-06-19 09:06:18 +02:00
tests dropping fsevents 2018-03-12 12:07:57 +01:00
.gitignore rewriting signal system 2018-04-22 13:01:01 +02:00
bin2carray.lua further structering mantle 2018-03-16 09:36:32 +01:00
ChangeLog moving default layer 1 to default.proto 2018-06-12 09:21:11 +02:00
CMakeLists.txt moving default layer 1 to default.proto 2018-06-12 09:21:11 +02:00
config.h.in cleanups 2018-03-13 16:09:41 +01:00
COPYING Fix documentation spelling bits, and a few links 2013-05-04 13:11:09 +10:00
distclean.sh rewriting signal system 2018-04-22 17:52:35 +02:00
INSTALL more READMEs 2018-03-22 09:23:00 +01:00
README.md further structering mantle 2018-03-16 09:36:32 +01:00
signames.sh reworking the signal system 2018-04-28 14:32:56 +02:00

Lsyncd -- Live Syncing (Mirror) Daemon

Description

Lsyncd watches a local directory trees event monitor interface (inotify or fsevents). It aggregates and combines events for a few seconds and then spawns one (or more) process(es) to synchronize the changes. By default this is rsync. Lsyncd is thus a light-weight live mirror solution that is comparatively easy to install not requiring new filesystems or block devices and does not hamper local filesystem performance.

Rsync+ssh is an advanced action configuration that uses a SSH to act file and directory moves directly on the target instead of re-transmitting the move destination over the wire.

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. This way simple, powerful and flexible configurations can be achieved. See the manual for details.

Lsyncd 3.0 requires rsync >= 3.1 on all source and target machines.

License: GPLv2 or any later GPL version.

When to use

Lsyncd is designed to synchronize a local directory tree with low profile of expected changes to a remote mirror. Lsyncd is especially useful to sync data from a secure area to a not-so-secure area.

Other synchronization tools

DRBD operates on block device level. This makes it useful for synchronizing systems that are under heavy load. Lsyncd on the other hand does not require you to change block devices and/or mount points, allows you to change uid/gid of the transferred files, separates the receiver through the one-way nature of rsync. DRBD is likely the better option if you are syncing databases.

GlusterFS and BindFS use a FUSE-Filesystem to interject kernel/userspace filesystem events.

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

TODO make new examples

You can find more examples in the manual.

Disclaimer

Besides the usual disclaimer in the license, we want to specifically emphasize that the authors, and any organizations the authors are associated with, can not be held responsible for data-loss caused by possible malfunctions of Lsyncd.