octoleo/lsyncd
1
0
Fork 0
mirror of https://github.com/octoleo/lsyncd.git synced 2024-12-04 19:03:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix spacing/wording

Browse Source
This commit is contained in:
Daniel Poelzleithner 2023-03-02 17:22:01 +01:00
parent d4fc88ba10
commit a4556b835f
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -16,8 +16,8 @@ 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. 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.
2-Way synchronization 2-way/bidirection synchronization
--------------------- ---------------------------------
It is not possible to use lsyncd to synchronize for example `folder1` with `folder2` and vice versa. Only one source to one target. Two way synchronization is a very hard problem that needs specialized tools. It is not possible to use lsyncd to synchronize for example `folder1` with `folder2` and vice versa. Only one source to one target. Two way synchronization is a very hard problem that needs specialized tools.
Imagine you start writing a very large file to `folder1`, lsyncd will start synchronizing this file to `folder2`, which might be on a different machine. The lsyncd on that machine will see a new file, and try to synchronize it back to `folder1`. If at the same time, you change bytes in this file, those changes will be overwritten with old data. Using lsyncd in such a way might work in practice, but data corruption is easily possible if you write into files afterwards. Imagine you start writing a very large file to `folder1`, lsyncd will start synchronizing this file to `folder2`, which might be on a different machine. The lsyncd on that machine will see a new file, and try to synchronize it back to `folder1`. If at the same time, you change bytes in this file, those changes will be overwritten with old data. Using lsyncd in such a way might work in practice, but data corruption is easily possible if you write into files afterwards.
`git-annex` is a good way to do this, if you don't mind working with git repositories. It stores each change as a revision that can be rolled back. `git-annex` is a good way to do this, if you don't mind working with git repositories. It stores each change as a revision that can be rolled back.

2
lsyncd.lua
View File

@ -5682,7 +5682,7 @@ OPTIONS:
-pidfile FILE Writes Lsyncds PID into FILE -pidfile FILE Writes Lsyncds PID into FILE
-runner FILE Loads Lsyncds lua part from FILE -runner FILE Loads Lsyncds lua part from FILE
-script FILE Script to load before execting runner (ADVANCED) -script FILE Script to load before execting runner (ADVANCED)
-sshopts Additional ssh command options when using rsyncssh -sshopts Additional ssh command options when using rsyncssh
-version Prints versions and exits -version Prints versions and exits
LICENSE: LICENSE: