aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Holger Weiss <holger@zedat.fu-berlin.de> 2012-06-22 17:11:18 +0200
committerGravatar Holger Weiss <holger@zedat.fu-berlin.de> 2012-06-22 17:11:18 +0200
commite6df238350588afd93f11501c4c673b07c9733a4 (patch)
tree14d75661adbb5e0046163a00c983721ebdd4bda8
parent4d5276273287ef59881b541ba96279e91974a4b2 (diff)
downloadmonitoring-plugins-e6df238350588afd93f11501c4c673b07c9733a4.tar.gz
Fix check_by_ssh test for non-Bash login shells
In the C shell and in the Z shell, the "?" character must be quoted or backslash-escaped in order to use it verbatim. Therefore, a command such as check_by_ssh -H test.example.com -l joe echo huh? might fail, depending on joe's login shell on test.example.com. Just to make sure, this commit removes most punctuation characters from our test strings.
-rw-r--r--plugins/t/check_by_ssh.t10
1 files changed, 5 insertions, 5 deletions
diff --git a/plugins/t/check_by_ssh.t b/plugins/t/check_by_ssh.t
index cca72c96..8d1b1904 100644
--- a/plugins/t/check_by_ssh.t
+++ b/plugins/t/check_by_ssh.t
@@ -27,11 +27,11 @@ plan skip_all => "SSH_HOST and SSH_IDENTITY must be defined" unless ($ssh_servic
plan tests => 42;
# Some random check strings/response
-my @responce = ('OK: Everything is fine!',
- 'WARNING: Hey, pick me, pick me!',
- 'CRITICAL: Shit happens...',
- 'UNKNOWN: What can I do for ya?',
- 'WOOPS: What did I smoke?',
+my @responce = ('OK: Everything is fine',
+ 'WARNING: Hey, pick me, pick me',
+ 'CRITICAL: Shit happens',
+ 'UNKNOWN: What can I do for ya',
+ 'WOOPS: What did I smoke',
);
my @responce_re;
my @check;