Public service announcement about this guide I put together for resetting
a csync2 cluster that's gotten thoroughly messed up. This is a last resort
approach but is useful when you're running every command you can think of
but just can't get the cluster cleanly running again:
https://gist.github.c
Hello,
My team is setting up csync2 on a small cluster, and I noticed there's a
RC for v2.0, but that was from last year without any recent commits or
updates. Has that been abandoned, or do you still plan to release it at
some point?
SCOTT BUCHANAN
Manager, Web Development & Engineering
eBay Ent
As to #1: csync2 does not integrate inotify, but you can connect it with
lsyncd to do that (substituting csync2 instead of rsync). I have written a
Puppet module that sets this up automatically that I plan on publishing
once I can polish it a bit more. If it would be helpful to you, let me
know and
It's documented in section 5.4 of the manual.
L means only present on the local host.
SCOTT BUCHANAN
Manager, Web Dev & Custom Engineering
eBay Enterprise
On 8/31/15, 1:04 PM, "Francisco Reyes" wrote:
>Is there a list somewhere of the status codes.
>
>Starting to use csync2 and I see the l
Csync2 runs on every host. However, two key points:
1. csync2 itself does not "detect" changes automatically to trigger a
sync. It has to be triggered by an outside system like lsyncd or cron.
2. csync2 is push only, so if you run it from Machine A in your example,
it will only ever push files to
