Re: [ClusterLabs Developers] New challenges with corosync 3/kronosnet + pacemaker

2018-02-12 Thread Jan Friesse
Ken Gaillot napsal(a): On Fri, 2018-02-09 at 12:52 -0500, Digimer wrote: On 2018-02-09 03:27 AM, Jan Pokorný wrote: Hello, there is certainly whole can of these worms, put first that crosses my mind: performing double (de)compression on two levels of abstraction in the inter-node communication

Re: [ClusterLabs Developers] New challenges with corosync 3/kronosnet + pacemaker

2018-02-12 Thread Christine Caulfield
On 12/02/18 08:04, Jan Friesse wrote: > Ken Gaillot napsal(a): >> On Fri, 2018-02-09 at 12:52 -0500, Digimer wrote: >>> On 2018-02-09 03:27 AM, Jan Pokorný wrote: Hello, there is certainly whole can of these worms, put first that crosses my mind: performing double (de)compressio

Re: [ClusterLabs Developers] Error when linking to libqb in shared library

2018-02-12 Thread Jan Pokorný
[let's move this to developers list] On 12/02/18 07:22 +0100, Kristoffer Grönlund wrote: > (and especially the libqb developers) > > I started hacking on a python library written in C which links to > pacemaker, and so to libqb as well, but I'm encountering a strange > problem which I don't know

Re: [ClusterLabs Developers] New challenges with corosync 3/kronosnet + pacemaker

2018-02-12 Thread Klaus Wenninger
On 02/12/2018 09:21 AM, Christine Caulfield wrote: > On 12/02/18 08:04, Jan Friesse wrote: >> Ken Gaillot napsal(a): >>> On Fri, 2018-02-09 at 12:52 -0500, Digimer wrote: On 2018-02-09 03:27 AM, Jan Pokorný wrote: > Hello, > > there is certainly whole can of these worms, put first

Re: [ClusterLabs Developers] [ClusterLabs] Error when linking to libqb in shared library

2018-02-12 Thread Kristoffer Grönlund
Jan Pokorný writes: > I guess you are linking your python extension with one of the > pacemaker libraries (directly on indirectly to libcrmcommon), and in > that case, you need to rebuild pacemaker with the patched libqb[*] for > the whole arrangement to work. Likewise in that case, as you may b