I would strongly recommend installing everything at the final
destination - in a changeroot
build environment if you don't want to taint your build-host.
Regards,
Klaus
On 03/02/2016 03:46 AM, Sharat Joshi wrote:
> Hi List Folk,
>
> I am very new to Pacemaker and I am trying to build using
Hi List Folk,
I am very new to Pacemaker and I am trying to build using sources.
After successfully installing libqb and corosync under
/disk1/software/libqb and /disk1/software/corosync and setting
$ export
Hi List Folk,
I am very new to Pacemaker and I am trying to build using sources.
After successfully installing libqb and corosync under
/disk1/software/libqb and /disk1/software/corosync and setting
$ export
On 03/01/2016 08:24 AM, Rafał Sanocki wrote:
> Hello
> Can you tell if that message is correct "
>
> #crm_mon -A
> Online: [ nodeA nodeB ]
> failover-ip1(ocf::pacemaker:wall): Started nodeB
> Clone Set: my-conn
> Started: [ nodeA nodeB ]
> Clone Set: my-connp
> Started: [ nodeA
On 26/02/16 07:58, Jan Pokorný wrote:
> On 26/02/16 14:27 +0900, Keisuke MORI wrote:
>> As of libqb-1.0rc3, Pacemaker fails to build upon it with the gcc
>> warnings as below.
>> There was no such a problem until 1.0rc2, and it seems that the
>> changes in the pull request #175 is related.
>>
>>
