From: Lon Hohberger <lhh@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Changes in libccs behaviour (PLEASE READ!)
Date: Tue, 10 Jun 2008 09:19:13 -0400 [thread overview]
Message-ID: <1213103953.20204.18.camel@ayanami.boston.devel.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0806031055250.5892@trider-g7>
On Tue, 2008-06-03 at 11:16 +0200, Fabio M. Di Nitto wrote:
> Hi guys,
>
> I just landed the last bits in libccs to support both xpath lite and full
> xpath queries. With this new code, a couple of things need to be checked
> across all applications using libccs.
>
> Relevant changes:
>
> ccs_connect() used to return only when cluster is quorated.
> This is not the case anymore. ccs_connect will return as soon as it can
> connect to aisexec and init properly (or fail).
> You can use cman_is_quorate from libcman for the same feature.
This is good - one of the things we've had happen in the past is the
"Not quorate/refusing connection" messages reported thousands of times.
I guess admins didn't like it :D
-- Lon
next prev parent reply other threads:[~2008-06-10 13:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 9:16 [Cluster-devel] Changes in libccs behaviour (PLEASE READ!) Fabio M. Di Nitto
2008-06-10 13:19 ` Lon Hohberger [this message]
2008-06-10 15:02 ` Fabio M. Di Nitto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1213103953.20204.18.camel@ayanami.boston.devel.redhat.com \
--to=lhh@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).