public inbox for cluster-cvs@sourceware.org help / color / mirror / Atom feed
From: Jan Friesse <honzaf@fedoraproject.org> To: cluster-cvs-relay@redhat.com Subject: fence-agents: master - fence_snmp_*: Add missed sys.path.apend to SNMP agents Date: Sun, 22 Mar 2009 14:22:00 -0000 [thread overview] Message-ID: <20090322142233.D21F7120212@lists.fedorahosted.org> (raw) Gitweb: http://git.fedorahosted.org/git/fence-agents.git?p=fence-agents.git;a=commitdiff;h=38493ef91b33d4ba4e6f4f6d5adebec936ca8c67 Commit: 38493ef91b33d4ba4e6f4f6d5adebec936ca8c67 Parent: 6f873faf451a3c7cb9bb0404a250c5de46d0ade0 Author: Jan Friesse <jfriesse@redhat.com> AuthorDate: Sun Mar 22 15:22:03 2009 +0100 Committer: Jan Friesse <jfriesse@redhat.com> CommitterDate: Sun Mar 22 15:22:03 2009 +0100 fence_snmp_*: Add missed sys.path.apend to SNMP agents If fencing.py and fencing_snmp.py is not installed in Python's search path, Python based fence agent will fall. This was (sadly) the case of SNMP based agents. This patch add sys.path.append to start of file, so everything should work now. --- fence/agents/apc_snmp/fence_apc_snmp.py | 1 + fence/agents/cisco_mds/fence_cisco_mds.py | 1 + fence/agents/ibmblade/fence_ibmblade.py | 1 + fence/agents/ifmib/fence_ifmib.py | 1 + fence/agents/intelmodular/fence_intelmodular.py | 1 + 5 files changed, 5 insertions(+), 0 deletions(-) diff --git a/fence/agents/apc_snmp/fence_apc_snmp.py b/fence/agents/apc_snmp/fence_apc_snmp.py index 8ffd7fc..8cdb169 100644 --- a/fence/agents/apc_snmp/fence_apc_snmp.py +++ b/fence/agents/apc_snmp/fence_apc_snmp.py @@ -9,6 +9,7 @@ # MN:AP7951 HR:B2) - SNMP v1 import sys, re, pexpect +sys.path.append("@FENCEAGENTSLIBDIR@") from fencing import * from fencing_snmp import * diff --git a/fence/agents/cisco_mds/fence_cisco_mds.py b/fence/agents/cisco_mds/fence_cisco_mds.py index 177c3b1..76a45d4 100644 --- a/fence/agents/cisco_mds/fence_cisco_mds.py +++ b/fence/agents/cisco_mds/fence_cisco_mds.py @@ -7,6 +7,7 @@ # with BIOS 1.0.16, kickstart 4.1(1c), system 4.1(1c) import sys, re, pexpect +sys.path.append("@FENCEAGENTSLIBDIR@") from fencing import * from fencing_snmp import * diff --git a/fence/agents/ibmblade/fence_ibmblade.py b/fence/agents/ibmblade/fence_ibmblade.py index 3c9ecf1..073da78 100644 --- a/fence/agents/ibmblade/fence_ibmblade.py +++ b/fence/agents/ibmblade/fence_ibmblade.py @@ -1,6 +1,7 @@ #!/usr/bin/python import sys, re, pexpect +sys.path.append("@FENCEAGENTSLIBDIR@") from fencing import * from fencing_snmp import * diff --git a/fence/agents/ifmib/fence_ifmib.py b/fence/agents/ifmib/fence_ifmib.py index 766a96d..0f955ac 100644 --- a/fence/agents/ifmib/fence_ifmib.py +++ b/fence/agents/ifmib/fence_ifmib.py @@ -9,6 +9,7 @@ # Only lance if is visible import sys, re, pexpect +sys.path.append("@FENCEAGENTSLIBDIR@") from fencing import * from fencing_snmp import * diff --git a/fence/agents/intelmodular/fence_intelmodular.py b/fence/agents/intelmodular/fence_intelmodular.py index 8cfa0ae..ea2453a 100644 --- a/fence/agents/intelmodular/fence_intelmodular.py +++ b/fence/agents/intelmodular/fence_intelmodular.py @@ -12,6 +12,7 @@ # Thanks Matthew Kent for original agent and testing. import sys, re, pexpect +sys.path.append("@FENCEAGENTSLIBDIR@") from fencing import * from fencing_snmp import *
reply other threads:[~2009-03-22 14:22 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090322142233.D21F7120212@lists.fedorahosted.org \ --to=honzaf@fedoraproject.org \ --cc=cluster-cvs-relay@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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).