From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] config: Add missing qdiskd options
Date: Wed, 12 Jan 2011 16:42:01 +0100 [thread overview]
Message-ID: <4D2DCBC9.2000204@redhat.com> (raw)
In-Reply-To: <1294844646-7333-1-git-send-email-lhh@redhat.com>
ACK?ed
Fabio
On 1/12/2011 4:04 PM, Lon Hohberger wrote:
> upgrade_wait, tko_up, use_uptime
>
> This is a clean cherry-pick in to the RHEL6 branch.
>
> Resolves: rhbz#645830
>
> Signed-off-by: Lon Hohberger <lhh@redhat.com>
> ---
> config/tools/xml/cluster.rng.in | 9 +++++++++
> 1 files changed, 9 insertions(+), 0 deletions(-)
>
> diff --git a/config/tools/xml/cluster.rng.in b/config/tools/xml/cluster.rng.in
> index ba5087b..2f34d6a 100644
> --- a/config/tools/xml/cluster.rng.in
> +++ b/config/tools/xml/cluster.rng.in
> @@ -295,6 +295,15 @@ To validate your cluster.conf against this schema, run:
> <attribute name="priority" rha:description="Scheduler priority. qdisk(5)." rha:sample=""/>
> </optional>
> <optional>
> + <attribute name="tko_up" rha:description="Amount of positive changes before a host is considered online. qdisk(5)." rha:sample=""/>
> + </optional>
> + <optional>
> + <attribute name="upgrade_wait" rha:description="Amount of cycles wait for conflicts for a bid for master status. qdisk(5)." rha:sample=""/>
> + </optional>
> + <optional>
> + <attribute name="use_uptime" rha:description="Use /proc/uptime instead of gettimeofday(). qdisk(5)." rha:sample=""/>
> + </optional>
> + <optional>
> <attribute name="stop_cman" rha:description="Stop cman if the quorum disk cannot be found during startup. qdisk(5)." rha:sample=""/>
> </optional>
> <optional>
next prev parent reply other threads:[~2011-01-12 15:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 15:04 [Cluster-devel] [PATCH] config: Add missing qdiskd options Lon Hohberger
2011-01-12 15:42 ` Fabio M. Di Nitto [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-01-12 15:09 Lon Hohberger
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=4D2DCBC9.2000204@redhat.com \
--to=fdinitto@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.