<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7638.1">
<TITLE>RE: [Nagios-users] Suse 10.0 - perl plugin return "No outpput"</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>> If you don't want to do that, write a C or shell wrapper that calls<BR>
> the plugin - you will have to rename the plugin so the wrapper can<BR>
> pretend to Nagios that it is the real plugin.<BR>
<BR>
Perhaps an easier way would be to specify the full path to Perl before any Perl plugin call:<BR>
<BR>
define command {<BR>
command_name check_ntp<BR>
command_line /usr/bin/perl $USER1$/check_ntp -H $HOSTADDRESS$<BR>
}<BR>
<BR>
<BR>
You could, of course, define the path to Perl in a macro, or even the path to Perl plus the path to the standard plugin dir in one macro, like:<BR>
<BR>
$USER2$=/usr/bin/perl /usr/lib/nagios/plugins # in resource.cfg<BR>
<BR>
<BR>
define command {<BR>
command_name check_ntp<BR>
command_line $USER2$/check_ntp -H $HOSTADDRESS$<BR>
}<BR>
<BR>
<BR>
We need more intelligible macro names, like $USER_PERL$.<BR>
<BR>
-John<BR>
</FONT>
</P>
</BODY>
</HTML>