From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 2/2] fence_wti: Unable to parse output when splitted into several screens (2/2)
Date: Wed, 16 Mar 2011 14:06:19 +0100 [thread overview]
Message-ID: <1300280779-16056-2-git-send-email-fdinitto@redhat.com> (raw)
In-Reply-To: <1300280779-16056-1-git-send-email-fdinitto@redhat.com>
From: Marek 'marx' Grac <mgrac@redhat.com>
Minor changes to previous patch. Power ON/OFF now works as expected
Resolves: rhbz#678522
---
fence/agents/wti/fence_wti.py | 3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/fence/agents/wti/fence_wti.py b/fence/agents/wti/fence_wti.py
index d05676b..8caa4c2 100644
--- a/fence/agents/wti/fence_wti.py
+++ b/fence/agents/wti/fence_wti.py
@@ -28,13 +28,12 @@ def get_power_status(conn, options):
conn.send("/S"+"\r\n")
if isinstance(options["-c"], list):
- re_all = options["-c"]
+ re_all = list(options["-c"])
else:
re_all = [options["-c"]]
re_next = re.compile("Enter: ", re.IGNORECASE)
re_all.append(re_next)
- conn.send("/S"+"\r\n")
result = conn.log_expect(options, re_all, int(options["-Y"]))
listing = conn.before
if result == (len(re_all) - 1):
--
1.7.4
next prev parent reply other threads:[~2011-03-16 13:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 13:06 [Cluster-devel] [PATCH 1/2] fence_wti: Unable to parse output when splitted into several screens Fabio M. Di Nitto
2011-03-16 13:06 ` Fabio M. Di Nitto [this message]
2011-03-16 13:57 ` [Cluster-devel] [PATCH 2/2] fence_wti: Unable to parse output when splitted into several screens (2/2) Lon Hohberger
2011-03-16 13:58 ` [Cluster-devel] [PATCH 1/2] fence_wti: Unable to parse output when splitted into several screens 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=1300280779-16056-2-git-send-email-fdinitto@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 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).