Module: check_mk
Branch: master
Commit: 50cfab0988ba0ec77547457f21fe3834cb6378d6
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=50cfab0988ba0e…
Author: Mathias Kettner <mk(a)mathias-kettner.de>
Date: Thu Feb 3 10:23:32 2011 +0100
Updated bug entries
---
.bugs/98 | 10 +++++++---
1 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/.bugs/98 b/.bugs/98
index 71ab2a2..2d91ae1 100644
--- a/.bugs/98
+++ b/.bugs/98
@@ -1,10 +1,11 @@
Title: Restart of Nagios makes Multisite murk
Component: multisite
+State: done
+Class: bug
+Date: 2011-01-22 14:20:58
Benefit: 2
-State: open
Cost: 2
-Date: 2011-01-22 14:20:58
-Class: bug
+Fun: 0
When Nagios is restarted (e.g. via WATO), then for a short time the
Livestatus socket is gone. This leads to error messages in various
@@ -14,3 +15,6 @@ errors.
We need to find a solution for a cleaner handling of this. Couldn't
be a site in the state "restarting". If yes - how can we detect such
a state. The livestatus socket is missing in such a case.
+
+2011-02-03 10:23:30: changed state open -> done
+jQuery was removed - the window is gone.