In our network we use 1.34 with actions where bash alias wrap around csync2
and clean sqlite's table with actions at all hosts throught ssh and then
normaly run csync2.
I was think that 2.0 fix this and now i am confused
On Oct 10, 2014 8:45 PM, "Łukasz Wąsikowski" <luk...@wasikowski.net> wrote:
> W dniu 2014-10-10 o 16:15, Lars Ellenberg pisze:
> > On Thu, Oct 09, 2014 at 02:18:03PM +0000, Buchanan, Scott wrote:
> >> 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?
> > I don't remember any complaints. Not sure what was keeping me from
> > tagging it a "release" as apposed to "candidate", iirc there had been
> > some build/packaging issues on some "platforms".
> > If I find the time to remember what was missing,
> > I'll clean it up and call it "release".
> > Meanwhile, just use it as is,
> > and report issues you are having here.
> I wanted to use actions, with 1.34 it was bugged - sometimes actions
> ended without errors and wasn't removed from active queue. It was fixed
> in 2.0, but 2.0 (at least 4c8bf2e2de9f21c6f2ad2d93851119ee16edd74a
> version) had another bug with actions (don't remember what was it though).
> best regards,
> Lukasz Wasikowski
> Csync2 mailing list
Csync2 mailing list