[Csync2] Csync2 2.0

[Łukasz Wąsikowski]

Exactly. I tried 4c8bf2e2de9f21c6f2ad2d93851119ee16edd74a to get rid of
this bug and got hit by another one linked with actions, but
unfortunatelly I don't remember what it was. I'll give 2.0 another try,
maybe it is fixed by now.

W dniu 2014-10-17 o 10:16, bes pisze:

> I'm talking about this bug in 1.34
> http://lists.linbit.com/pipermail/csync2/2008-July/000421.html
> 
> On Thu, Oct 16, 2014 at 4:09 PM, Lars Ellenberg
> <lars.ellenberg at linbit.com <mailto:lars.ellenberg at linbit.com>> wrote:
> 
>     On Sat, Oct 11, 2014 at 12:22:31PM +0300, bes wrote:
>     > 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
> 
>     I have no idea what you guys are talking about.
> 
>     >  On Oct 10, 2014 8:45 PM, "Łukasz Wąsikowski" <lukasz at wasikowski.net <mailto:lukasz at 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