solotimes / lsyncd

Automatically exported from code.google.com/p/lsyncd
GNU General Public License v2.0
0 stars 0 forks source link

lsyncd fails on rsync versions not supporting -d option #10

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
Try to sync with a rsync version that doesn't support -d option (eg. < 2.6.4).

What is the expected output? What do you see instead?
During normal operations, directories should sync, but the following output
is generated:

rsync: on remote machine: -ldtp: unknown option
rsync error: syntax or usage error (code 1) at main.c(1002)
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(600)
[sender=3.0.6]

What version of the product are you using? On what operating system?
lsyncd 1.26
rsync 3.0.6 on source machine
rsync 2.6.2 on remote machine

Please provide any additional information below.
Initial sync works as expected (lsyncd uses -r during startup). I'm tempted
to always add -r option in lsyncd configuration file, but I'm not sure if
it can cause bad side effects. After all lsyncd uses -d for a reason, isn't it?

Original issue reported on code.google.com by davide.r...@gmail.com on 5 Nov 2009 at 9:58

GoogleCodeExporter commented 9 years ago
Using always -r seems to solve the problem. Probably -d is used to optimize 
performance.

Original comment by davide.r...@gmail.com on 5 Nov 2009 at 10:22

GoogleCodeExporter commented 9 years ago
the performace is likey worse if running always with -r, otherwise i dont see 
something bad regarding ensuring the data gets over there.

Original comment by axk...@gmail.com on 11 Jul 2010 at 7:47