[deployment-guide/comm-rel: 184/727] Added the Testing the Configuration section.

[Jaromir Hradilek]

commit e788b1797973561bc4735b5d3c6007355ac60c9e
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Wed Jul 28 15:27:48 2010 +0200

    Added the Testing the Configuration section.

 en-US/The_kdump_Crash_Recovery_Service.xml |   31 ++++++++++++++++++++++++++++
 1 files changed, 31 insertions(+), 0 deletions(-)
---
diff --git a/en-US/The_kdump_Crash_Recovery_Service.xml b/en-US/The_kdump_Crash_Recovery_Service.xml
index d2c2504..5aacf6c 100644
--- a/en-US/The_kdump_Crash_Recovery_Service.xml
+++ b/en-US/The_kdump_Crash_Recovery_Service.xml
@@ -100,6 +100,37 @@
         </figure>
       </section>
     </section>
+    <section id="s2-kdump-configuration-testing">
+      <title>Testing the Configuration</title>
+      <warning>
+        <title>Caution: Be Careful When Using These Commands</title>
+        <para>
+          The commands below will cause the kernel to crash. Use caution when following these steps, and by no means use them on a production machine.
+        </para>
+      </warning>
+      <para>
+        To test the configuration, reboot the system with <systemitem class="service">kdump</systemitem> enabled, and make sure that the service is running (refer to <xref linkend="s1-services-running" /> for more information on how to run a service in &MAJOROS;):
+      </para>
+      <screen>~]# <command>service kdump status</command>
+Kdump is operational</screen>
+      <para>
+        Then type the following commands at a shell prompt:
+      </para>
+      <screen>~]# <command>echo 1 > /proc/sys/kernel/sysrq</command>
+~]# <command>echo c > /proc/sysrq-trigger</command></screen>
+      <para>
+        This will force the Linux kernel to crash, and the <filename><replaceable>address</replaceable>-<replaceable>YYYY-MM-DD</replaceable>-<replaceable>HH:MM:SS</replaceable>/vmcore</filename> file will be copied to the location you have selected in the configuration (that is, to <filename class="directory">/var/crash/</filename> by default).
+      </para>
+      <example id="ex-kdump-configuration-testing-vmcore">
+        <title>Listing a content of <filename class="directory">/var/crash/</filename> after a crash</title>
+        <screen>~]# <command>tree --charset=ascii /var/crash</command>
+/var/crash
+`-- 127.0.0.1-2010-07-28-16:58:36
+    `-- vmcore
+
+1 directory, 1 file</screen>
+      </example>
+    </section>
   </section>
   <section id="s1-kdump-resources">
     <title>Additional Resources</title>