Hi Andrew,
I confirmed some problems, but seem to be caused by the fact thatÂ
an event
occurs somehow or other in g_main_loop of lrmd in the period when it is
shorter
than a monitor.
So if you create a trivial program with g_main_loop and a timer, and
then change
the system
All,
it's been almost 6 years since we had a face to face meeting for all
developers and vendors involved in Linux HA.
I'd like to try and organize a new event and piggy-back with DevConf in
Brno [1].
DevConf will start Friday the 6th of Feb 2015 in Red Hat Brno offices.
My suggestion would be
On 8 Sep 2014, at 7:12 pm, renayama19661...@ybb.ne.jp wrote:
Hi Andrew,
I confirmed some problems, but seem to be caused by the fact that
an event
occurs somehow or other in g_main_loop of lrmd in the period when it is
shorter
than a monitor.
So if you create a trivial program
On 08/09/14 06:30 AM, Fabio M. Di Nitto wrote:
All,
it's been almost 6 years since we had a face to face meeting for all
developers and vendors involved in Linux HA.
I'd like to try and organize a new event and piggy-back with DevConf in
Brno [1].
DevConf will start Friday the 6th of Feb 2015
On Sat, Sep 06, 2014 at 02:14:29PM -0400, David Magda wrote:
On Sep 6, 2014, at 12:00, Ken Gaillot kjgai...@gleim.com wrote:
# This allows slapd to run on both hosts.
clone ldap-daemon-clone ldap-daemon meta globally-unique=false
interleave=true
[...]
I'll give it a go.
This worked.
On 09/08/2014 11:02 AM, David Magda wrote:
On Sat, Sep 06, 2014 at 02:14:29PM -0400, David Magda wrote:
On Sep 6, 2014, at 12:00, Ken Gaillot kjgai...@gleim.com wrote:
# This allows slapd to run on both hosts.
clone ldap-daemon-clone ldap-daemon meta globally-unique=false
interleave=true
*From:* Andrew Beekhof and...@beekhof.net
*Sent:* 2014-09-02 02:58:53 EDT
*To:* The Pacemaker cluster resource manager pacemaker@oss.clusterlabs.org
*Subject:* Re: [Pacemaker] pacemaker-remote container as a clone resource
Is it possible to put a location constraint on a resource such that it
will only run on a pacemaker-remote node? Or vice-versa, so that a
resource will not run on a pacemaker-remote node?
At a glance, this doesn't seem possible as the pacemaker-remote node
does not exist as a node entry in the
