cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Christine Caulfield <ccaulfie@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] compare cluster name in cman daemon
Date: Wed, 25 May 2011 09:05:05 +0100	[thread overview]
Message-ID: <4DDCB831.9050808@redhat.com> (raw)
In-Reply-To: <4DDCAE8B.2000401@openvz.org>

On 25/05/11 08:23, Evgeniy Sokolov wrote:
> if length of cluster name = 16, last char of msg->clustername will not
> be zero.
> In this case strcmp will continue read member fence_agent from
> cl_transmsg structure.
>
>

If the length of the cluster name = 16 then there is a bug somewhere 
else that needs fixing ;-)

Chrissie



  reply	other threads:[~2011-05-25  8:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-25  7:23 [Cluster-devel] [PATCH] compare cluster name in cman daemon Evgeniy Sokolov
2011-05-25  8:05 ` Christine Caulfield [this message]
2011-05-25  8:37   ` Evgeniy Sokolov
2011-05-30  8:45     ` Evgeniy Sokolov
2011-05-31  7:40       ` Christine Caulfield
2011-05-30  9:06   ` Dmitry Mishin

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=4DDCB831.9050808@redhat.com \
    --to=ccaulfie@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).