1.2 BUG with state retention?

jschmoe goddamnit at jen-uine.com
Wed Mar 31 00:22:04 CEST 2004


I guess nobody else uses program state retention.
I located the bug (the order that the program state info is written/read differs)

Here's the patch that fixes the issue:

diff -uNr nagios-1.2-orig/xdata/xrddefault.c nagios-1.2/xdata/xrddefault.c
--- nagios-1.2-orig/xdata/xrddefault.c	Mon Feb  2 17:36:08 2004
+++ nagios-1.2/xdata/xrddefault.c	Tue Mar 30 15:17:52 2004
@@ -181,7 +181,7 @@
 
 	/* save program state information */
 	get_program_state_information(&enable_notifications,&execute_service_checks,&accept_passive_service_checks,&enable_event_handlers,&obsess_over_services,&enable_flap_detection,&enable_failure_prediction,&process_performance_data);
-	snprintf(temp_buffer,sizeof(temp_buffer)-1,"PROGRAM: %d;%d;%d;%d;%d;%d;%d;%d\n",enable_notifications,accept_passive_service_checks,execute_service_checks,enable_event_handlers,obsess_over_services,enable_flap_detection,enable_failure_prediction,process_performance_data);
+	snprintf(temp_buffer,sizeof(temp_buffer)-1,"PROGRAM: %d;%d;%d;%d;%d;%d;%d;%d\n",enable_notifications,execute_service_checks,accept_passive_service_checks,enable_event_handlers,obsess_over_services,enable_flap_detection,enable_failure_prediction,process_performance_data);
 	temp_buffer[sizeof(temp_buffer)-1]='\x0';
 	fputs(temp_buffer,fp);
 

-jschmoe

> I just upgraded from 1.1  Previously I had program state retention
> enabled, and it was working fine.  Now it seems broke with 1.2.


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
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





More information about the Users mailing list