Hi All,
We have a question for the next correction.
*
https://github.com/ClusterLabs/pacemaker/commit/a97c28d75347aa7be76092aa22459f0f56a220ff
We understand it that this obeyed a correction of systemd.
In Pacemaker1.1.13, SysVStartPriority=99 is set.
Pacemaker1.1.12 is set, too.
When we
On 06/08/15 15:42 +0900, renayama19661...@ybb.ne.jp wrote:
We have a question for the next correction.
*
https://github.com/ClusterLabs/pacemaker/commit/a97c28d75347aa7be76092aa22459f0f56a220ff
We understand it that this obeyed a correction of systemd.
In Pacemaker1.1.13,
Hi,
following illustrates what happens with 'crm configure show' output after
playing with 'crm node standby|online' having some node attributes already set
from
the loaded config.
xml node id=1 uname=dell71 \
instance_attributes id=dell71-instance_attributes \
nvpair
Hi Jan,
Thank you for comments.
When we use Pacemaker1.1.12, does it have a problem to delete
SysVStartPriority=99?
Or must we not delete it when use Pacemaker1.1.12 and Pacemaker1.1.13?
Or is it necessary to judge it by a version of systemd of the OS, and to
set it?
It was a leftover
Thanks, resolved.
I ran into the following libqb issue:
https://github.com/ClusterLabs/libqb/issues/139
https://github.com/ClusterLabs/libqb/pull/141
Applying 7f56f58 on libqb 0.17.1 fixed my problem.
https://github.com/davidvossel/libqb/commit/7f56f583d891859c94b24db0ec38a301c3f3466a.patch
On tor, 2015-08-06 at 18:01 +0300, Vladislav Bogdanov wrote:
Hi,
following illustrates what happens with 'crm configure show' output
after
playing with 'crm node standby|online' having some node attributes
already set from
the loaded config.
xml node id=1 uname=dell71 \
