Revision: 243
Author: martin2812
Date: Wed Sep 15 05:55:30 2010
Log: The monitoring state update from state file on monit start reseted the
service's initializing state
so bunch of values which were not initialized yet were displayed when monit
status was called
immediately after monit start.
http://code.google.com/p/monit/source/detail?r=243
Modified:
/trunk/CHANGES.txt
/trunk/state.c
=======================================
--- /trunk/CHANGES.txt Wed Sep 15 05:36:51 2010
+++ /trunk/CHANGES.txt Wed Sep 15 05:55:30 2010
@@ -116,12 +116,11 @@
between two monitoring cycles while cpu monitoring was initializing.
Thanks to
Marcus Muelbuesch for report.
-* Fixed division by zero when 'monit status' was called immediately after
monit
- start before service was initialized.
-
* Fixed display of port response time as -1 in 'monit status' if it was
called in
the middle of service test.
+* Fixed display of initializing state for services after monit start or
reload.
+
Version 5.1.1
=======================================
--- /trunk/state.c Fri Jan 8 03:20:43 2010
+++ /trunk/state.c Wed Sep 15 05:55:30 2010
@@ -270,5 +270,7 @@
static void update_service_state(Service_T service, State_T *state) {
service->nstart= state->nstart;
service->ncycle= state->ncycle;
- service->monitor= state->monitor;
-}
+ /* Keep services in initializing state unless the monitoring should be
disabled */
+ if (state->monitor == MONITOR_NOT)
+ service->monitor= state->monitor;
+}
_______________________________________________
monit-dev mailing list
monit-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/monit-dev
