ePN patch. [SEC=UNCLASSIFIED]

[Stanley.Hopcroft at Dest.gov.au]

Dear Larry,

I am writing to thank you for your letter and say, 

> -----Original Message-----
> 
> Check the SVN, I submitted a small patch for this.  You may have had a

> better way to do it as I don't do heavy development.
> 

(CVS ?)

Cool !

-# p1.pl for Nagios 2.0
+# p1.pl for Nagios
 
 use strict ;
 
@@ -201,6 +201,13 @@
 								#
Suppress warning display.
 	local $SIG{__WARN__}			= \&throw_exception ;
 
+
+                                                                #
Following 3 lines added 10/18/07 by Larry Low to fix problem where
+                                                                #
modified Perl plugins didn't get recached by the epn
+        no strict 'refs';
+        undef %{$package.'::'};
+        use strict 'refs';
+
 								#
Compile &$package::hndlr. Since non executable code is being eval'd
 								# there
is no need to protect lexicals in this scope.
 	eval $hndlr;

My patch used Symbol qw(delete_package) ; this is a much better way.
(for bonus marks, fix the leak [or reduce it's rate]).

For the benefit of the list:

As far as I can see, Larry's patch should do what my patch intended to
do - namely eliminate spurious compilation failures after a Perl plugin
is modified - but better, so testing of that patch is unnecessary.

Yours sincerely.



Classification: UNCLASSIFIED

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Nagios-users mailing list
Nagios-users at 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