Changes between Version 3 and Version 4 of doc/usage/nscp/crash

Timestamp:

12/26/10 17:05:20 (2 years ago)

Author:

mickem

Comment:

--

doc/usage/nscp/crash

@@ -26 +26 @@
 I would probably advice people to think about which strategy is the right one for you but for me this high impact points are sensitivity and firewall issues related to submissions. Which can be circumvented by sending the archived files manually from a server which can access the Internet.
 
+
+== Configuring crash detection and actions ==
+
+To get you started I have divided this guide into three sections but nothing keeps you (and I advocate when possible) from using all three of these methods.
+
 == Archiving files ==
+
+The simplest way to protect your self is to make yourself aware of the fact that NSClient++ has crashed. This is done using both the archive feature and the [[check_nscp]] command in addition to this archiving crash dump files makes it possible to submit them by hand afterwards if you have an issue you want me to help you resolve. Submitting the crash dumps are fairly simple and you can either use the reporter tool or just send them via email to me.
+
+Archiving is the default action and it is enable by default.
+{{{
+[crash]
+; Archive crash dump files if a crash is detected
+;archive=1
+
+; Submit crash reports to a crash report server (this overrrides archive)
+;submit=0
+
+; Restart service if a crash is detected
+;restart=1
+}}}
+
+To disable archiving you use the following instead:
+{{{
+[crash]
+; Archive crash dump files if a crash is detected
+archive=0
+}}}
+
+Once NSClient++ crashes two files are crated;
+ 1. <GUID>.dmp) is the actual dumped data (stack traces and variable contents)
+ 2. <GUID>.dmp.txt is a description file with some meta information about NSClient++
+
+To be able to check the health of NSClient++ you need to enable the [[CheckNSCP.dll]] module.
+Which is done like so:
+{{{
+[modules]
+; ...
+CheckNSCP.dll
+; ...
+}}}
+
+The module serves two purposes the first being to collect all error messages reported inside NSClient++ and the second being to check the crash dump folder for crash dumps.
+
+
+
+
+