Module: check_mk
Branch: master
Commit: 16603db35bf681560f466a568339606dd22d59aa
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=16603db35bf681…
Author: Mathias Kettner <mk(a)mathias-kettner.de>
Date: Fri Dec 20 15:39:15 2013 +0100
Udpated description of Werk
---
.werks/437 | 14 ++++++++------
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/.werks/437 b/.werks/437
index f785a45..bea4eab 100644
--- a/.werks/437
+++ b/.werks/437
@@ -5,17 +5,19 @@ Version: 1.2.5i1
Date: 1387549981
Class: feature
-Do you know the plugin output <i>invalid output from agent, invalid check
parameters or ...</i>?
-The option for debugging such failed checks has been converted from an absolute
-path to a simple Checkbox. The target path for the log file is now hardcoded
-and will be printed by the failed check in the plugin output.
+Do you know the plugin output <i>invalid output from agent, invalid check
+parameters or ...</i>? The option for debugging such failed checks has
+been converted from an absolute path to a simple Checkbox. The target path
+for the log file is now hardcoded and will be printed by the failed check
+in the plugin output. The advantage is that when using OMD the option
+will work on all sites of a distributed environment and will log to
+<tt>var/log/check_mk/crashed-checks.log</tt> within the site.
-Existing configuration will not be touched, though, and honor the configured
+Existing configurations will not be touched, though, and honor the configured
path - as long as you do not change the option via WATO. <tt>main.mk</tt>
still
allows the old way:
F+:main.mk
-
# Hard code path to log file
debug_log = "/var/log/foo.log"