On 29/11/16 08:24 +0100, Ulrich Windl wrote:
> Some servers first fork and exit, virtually being successful
> immediately, while the child (the "server loop") could die a moment
> later. Finding the perfect time to wait for the server dying is kind
> of black magic ;-)
That's exactly why I thing t
On 30/11/16 14:05 -0600, Ken Gaillot wrote:
> ClusterLabs is proud to announce the latest release of the Pacemaker
> cluster resource manager, version 1.1.15. The source code is available at:
>
> https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-1.1.16
In the same vein as recent lib
Le 1 décembre 2016 17:39:45 GMT+01:00, Ken Gaillot a
écrit :
>On 12/01/2016 10:13 AM, Jehan-Guillaume de Rorthais wrote:
>> On Wed, 30 Nov 2016 14:05:19 -0600
>> Ken Gaillot wrote:
>>
>>> ClusterLabs is proud to announce the latest release of the Pacemaker
>>> cluster resource manager, versio
On 12/01/2016 10:13 AM, Jehan-Guillaume de Rorthais wrote:
> On Wed, 30 Nov 2016 14:05:19 -0600
> Ken Gaillot wrote:
>
>> ClusterLabs is proud to announce the latest release of the Pacemaker
>> cluster resource manager, version 1.1.15.
>
> 1.1.6 I guess ;)
Whoops!
Well now I don't feel so bad
On Wed, 30 Nov 2016 14:05:19 -0600
Ken Gaillot wrote:
> ClusterLabs is proud to announce the latest release of the Pacemaker
> cluster resource manager, version 1.1.15.
1.1.6 I guess ;)
But congrats anyway !
> * Previously, the OCF_RESKEY_CRM_meta_notify_active_* variables were not
> properly
Thank you for the comprehensive answer. =)
Thank you,
Kostia
On Thu, Dec 1, 2016 at 5:56 PM, Ken Gaillot wrote:
> On 12/01/2016 06:04 AM, Kostiantyn Ponomarenko wrote:
> > OK, now I see. I still have a few questions.
> > 1. Is there a good reason to not remove the attribute totally if it
>
On 12/01/2016 06:04 AM, Kostiantyn Ponomarenko wrote:
> OK, now I see. I still have a few questions.
> 1. Is there a good reason to not remove the attribute totally if it
> is "deleted"?
We do this for two reasons:
1. You can "delete" an attribute for just one node, while leaving it on
other
On 30/11/16 12:10 -0300, Ronny Machado C. wrote:
> soon I'll have to configure an Apache web server cluster which publish a
> VIP via ofc:hearbeat:IPaddr2, thing is, the two nodes live in different
> sites and with a different ip segments...any advice on how to
> use ocf:heartbeat:IPaddr2 ip=x.x.
On 12/01/2016 01:15 AM, Ulrich Windl wrote:
Ken Gaillot schrieb am 30.11.2016 um 21:39 in
Nachricht
> <62cb811f-4396-ff36-ec03-67000b4ed...@redhat.com>:
>
> [...]
>> Once set, attributes are not truly deleted -- only their values are
>> cleared. And --delay has no effect with --update
OK, now I see. I still have a few questions.
1. Is there a good reason to not remove the attribute totally if it is
"deleted"?
2. Does "attrd_updater" sets attributes to "status" configuration
section only?
3. Do I need to modify/set "--delay" to 0 before removing or changing
the attrib
Thanks a bunch for the advice, but finally is easier than I thought, I will
simply use a different configuration for each apache server, but still
maintaning replication via DRBD (DB/FS).
Again, thanks for the reply @Dimitri.
Hugs from Chile!!
*---*
*Ronny Machado C.*
* IT Consultant*
* +56
11 matches
Mail list logo