From caf9ce72ff6e708dadd85ee1677439f41694f287 Mon Sep 17 00:00:00 2001 From: Stanley Hopcroft Date: Tue, 23 Nov 2004 00:06:49 +0000 Subject: trivial changes to Perl plugin section. git-svn-id: https://nagiosplug.svn.sourceforge.net/svnroot/nagiosplug/nagiosplug/trunk@924 f882894a-f735-0410-b71e-b25c423dba1c --- doc/developer-guidelines.sgml | 19 ++++++++++++------- 1 file changed, 12 insertions(+), 7 deletions(-) (limited to 'doc') diff --git a/doc/developer-guidelines.sgml b/doc/developer-guidelines.sgml index 064bd924..9ec3f94e 100644 --- a/doc/developer-guidelines.sgml +++ b/doc/developer-guidelines.sgml @@ -407,12 +407,12 @@ Do not use BEGIN and END blocks since they will be called - the first time and when Nagios shuts down with Embedded Perl (ePN). In + only once (when Nagios starts and shuts down) with Embedded Perl (ePN). In particular, do not use BEGIN blocks to initialize variables. To use utils.pm, you need to provide a full path to the - module in order for it to work with ePN. + module in order for it to work. e.g. @@ -429,16 +429,18 @@ variable. - Explicitly initialize each varialable in use. Otherwise with - caching enabled, the plugin will not be recompilied each time, and + Explicitly initialize each variable in use. Otherwise with + caching enabled, the plugin will not be recompiled each time, and therefore Perl will not reinitialize all the variables. All old variable values will still be in effect. - Do not use > DATA < (these simply do not compile under ePN). + Do not use >DATA< handles (these simply do not compile under ePN). - Do not use named subroutines + Do not use global variables in named subroutines. This is bad practise anyway, but with ePN the + compiler will report an error "<global_var> will not stay shared ..". Values used by + subroutines should be passed in the argument list. If writing to a file (perhaps recording @@ -449,7 +451,10 @@ As in all plugins need to monitor their runtime, specially if they are using network - resources. Use of the alarm is recommended. + resources. Use of the alarm is recommended + noting that some Perl modules (eg LWP) manage timers, so that an alarm + set by a plugin using such a module is overwritten by the module. + (workarounds are cunning (TM) or using the module timer) Plugins may import a default time out ($TIMEOUT) from utils.pm. -- cgit v1.2.3-74-g34f1