Lsyncd (Live Syncing Daemon) synchronizes local directories with remote targets
Go to file
2012-10-02 18:53:27 +02:00
doc manpage update 2012-04-04 15:52:36 +02:00
examples removing extra linespaces, comment cleanup 2012-09-07 08:58:44 +02:00
m4 Try harder to find matching Lua program/library pairs 2012-10-02 15:58:52 +02:00
tests removed e2s to reduce weak tables logic complexity 2012-03-21 11:39:52 +01:00
.gitignore luac.c is no longer generated 2012-03-23 10:01:28 +01:00
autogen.sh coded a lua hello world 2010-10-14 13:52:01 +00:00
bin2carray.lua fix script integration 2011-05-04 13:18:37 +00:00
ChangeLog forgot date in Changelog :-/ 2012-04-04 14:00:52 +02:00
configure.ac Check whether Lua library was compiled with compat support 2012-10-02 18:53:27 +02:00
COPYING gpl info 2010-11-16 21:28:46 +00:00
default-direct.lua Correct small syntax error/typo 2012-03-15 10:07:42 +08:00
default-rsync.lua fixing new rsync argument computation 2012-10-02 08:25:46 +02:00
default-rsyncssh.lua _extra will be the generic future extender, if someone absoletly must do it 2012-10-01 21:36:23 +02:00
default.lua fixing settings.insist ignore by default 2012-09-07 18:00:52 +02:00
fsevents.c code beautification 2012-01-27 12:08:10 +01:00
inotify.c Use LSYNCD_*LIBNAME to refer to lsyncd/.inotify tables 2012-10-02 02:56:29 +02:00
lsyncd.c Use LSYNCD_*LIBNAME to refer to lsyncd/.inotify tables 2012-10-02 02:56:29 +02:00
lsyncd.h Use LSYNCD_*LIBNAME to refer to lsyncd/.inotify tables 2012-10-02 02:56:29 +02:00
lsyncd.lua code beautifications 2012-10-02 08:35:31 +02:00
Makefile.am Use modern AM_INIT_AUTOMAKE and store aclocal stuff in separate m4/ dir 2012-10-02 15:30:05 +02:00
README.md Manual is now on github 2012-04-14 23:18:19 +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 blockdevices 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 retransmitting the move destination over the wire.

Fine-grained customizaton 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 simplicity can be balanced with powerfulness. See the manual for details Lsyncd20Manual

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.

Lsyncd usage examples

lsyncd -rsync /home remotehost.org::share/

This watches and rsycn´s the local directory /home with all subdirectories and transfers them to 'remotehost' using the rsync-share 'share'.

lsyncd -rsyncssh /home remotehost.org backup-home/

This will also rsync/watch '/home', but it uses a ssh connection to make moves local on the remotehost instead of retransmitting the moved file over the wire.

Some more complicated examples, tips and tricks you can find in the Lsyncd20Manual.

Disclaimer

Besides the usual disclaimer in the license, we want to specifically emphasize that neither the authors nor any organization the authors are associated with can and will hold responsible for data-loss caused by possible malfunctions of Lsyncd.