Am Montag, 11. September 2006 00:55 schrieb John Daily:
> > If you don't want to do that, write a C or shell wrapper that calls
> > the plugin - you will have to rename the plugin so the wrapper can
> > pretend to Nagios that it is the real plugin.
>
> Perhaps an easier way would be to specify the full path to Perl before any
> Perl plugin call:
>
> define command {
> command_name check_ntp
> command_line /usr/bin/perl $USER1$/check_ntp -H $HOSTADDRESS$
> }
>
>
> 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:
Hi John,
thist is a very good tip thanks !
There are many perl plugins on NagiosExchange.org which are not testet to work
with ePN
I think Plugins should be tagged by the developer.
For example:
# EPN_TESTED
in Line 2
So nagios uses ePN only for tagged plugins.
What do you think ?
Jörg
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
