[Nagiosplug-devel] RFC: Nagios 3 and Embedded Perl Plugins
Florian Gleixner
flo at bier.homeip.net
Mon Jan 1 01:07:56 CET 2007
Hi,
is there or is it planned to support some time plugins that are compiled
as dynamic libraries and can be loaded with dlopen()?
The embedded perl is very nice and makes plugin development fast, but a
C/C++ api with dynamically loaded plugins could make nagios much faster.
Flo
Ethan Galstad wrote:
> Hi Everyone -
>
> One of the things that Nagios 3 will support is the ability to use the
> embedded Perl interpreter for specific perl plugins only, instead of all
> or nothing. The Nagios 3 development code currently support the
> following...
>
> Line 2 of a Perl plugin may start with one of the following:
>
> #USE_EPN
>
> -or-
>
> #NO_EPN
>
> If the #USE_EPN statement is found, Nagios will use the embedded Perl
> interpreter to run the plugin. If #NO_EPN is found, it will not be used
> (even if epn is compiled in and enabled in the Nagios daemon). If
> neither directive is found, Nagios will default to the behavior
> specified by a new 'use_embedded_perl_implicitly' variable in the main
> Nagios config file.
>
> Plugin devs - would you prefer different statements other than #USE_EPN
> / #NO_EPN, or are they okay? Any other comments or suggestions?
>
>
> Ethan Galstad,
> Nagios Developer
> ---
> Email: nagios at nagios.org
> Website: http://www.nagios.org
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________________
> Nagios Plugin Development Mailing List Nagiosplug-devel at lists.sourceforge.net
> Unsubscribe at https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel
> ::: Please include plugins version (-v) and OS when reporting any issue.
> ::: Messages without supporting info will risk being sent to /dev/null
>
More information about the Devel
mailing list