[deployment-guide: 122/185] Refactoring...

[Jaromir Hradilek]

commit 90502b047b4656be96ad53fcc660773b81b2b515
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Fri Mar 11 18:10:12 2011 +0100

    Refactoring...

 en-US/The_kdump_Crash_Recovery_Service.xml |   49 +++++++++++++++++-----------
 1 files changed, 30 insertions(+), 19 deletions(-)
---
diff --git a/en-US/The_kdump_Crash_Recovery_Service.xml b/en-US/The_kdump_Crash_Recovery_Service.xml
index 8aad7e4..51c92bd 100644
--- a/en-US/The_kdump_Crash_Recovery_Service.xml
+++ b/en-US/The_kdump_Crash_Recovery_Service.xml
@@ -588,7 +588,7 @@ Kdump is operational</screen>
       <see><application>crash</application></see>
     </indexterm>
     <para>
-      To determine the cause of the system crash, you can use the <application>crash</application> utility. This utility allows you to interactively analyze a running Linux system as well as a core dump created by <systemitem>netdump</systemitem>, <systemitem>diskdump</systemitem>, <systemitem>xendump</systemitem>, or <systemitem>kdump</systemitem>. When started, it presents you with an interactive prompt very similar to the GNU Debugger (GDB).
+      To determine the cause of the system crash, you can use the <application>crash</application> utility, which provides an interactive prompt very similar to the GNU Debugger (GDB). This utility allows you to interactively analyze a running Linux system as well as a core dump created by <systemitem>netdump</systemitem>, <systemitem>diskdump</systemitem>, <systemitem>xendump</systemitem>, or <systemitem>kdump</systemitem>.
     </para>
     <indexterm>
       <primary><application>crash</application></primary>
@@ -605,20 +605,22 @@ Kdump is operational</screen>
         For more information on how to install new packages in &MAJOROS;, refer to <xref linkend="sec-Installing" />.
       </para>
     </note>
-    <indexterm>
-      <primary><application>crash</application></primary>
-      <secondary>opening the dump image</secondary>
-    </indexterm>
-    <para>
-      To start the utility, type the command in the following form at a shell prompt:
-    </para>
-    <screen><command>crash /var/crash/<replaceable>timestamp</replaceable>/vmcore /usr/lib/debug/lib/modules/<replaceable>kernel</replaceable>/vmlinux</command></screen>
-    <para>
-      Note that the <replaceable>kernel</replaceable> version should be the same that was captured by <systemitem class="service">kdump</systemitem>. To find out which kernel you are currently running, use the <command>uname -r</command> command.
-    </para>
-    <example id="ex-kdump-crash-running">
-      <title>Running the <command>crash</command> utility</title>
-      <screen>~]# <command>crash /usr/lib/debug/lib/modules/2.6.32-69.el6.i686/vmlinux \</command>
+    <section id="s2-kdump-crash-running">
+      <title>Running the <application>crash</application> Utility</title>
+      <indexterm>
+        <primary><application>crash</application></primary>
+        <secondary>opening the dump image</secondary>
+      </indexterm>
+      <para>
+        To start the utility, type the command in the following form at a shell prompt:
+      </para>
+      <screen><command>crash /var/crash/<replaceable>timestamp</replaceable>/vmcore /usr/lib/debug/lib/modules/<replaceable>kernel</replaceable>/vmlinux</command></screen>
+      <para>
+        Note that the <replaceable>kernel</replaceable> version should be the same that was captured by <systemitem class="service">kdump</systemitem>. To find out which kernel you are currently running, use the <command>uname -r</command> command.
+      </para>
+      <example id="ex-kdump-crash-running">
+        <title>Running the <application>crash</application> utility</title>
+        <screen>~]# <command>crash /usr/lib/debug/lib/modules/2.6.32-69.el6.i686/vmlinux \</command>
 <command>/var/crash/127.0.0.1-2010-08-25-08:45:02/vmcore</command>
 
 crash 5.0.0-23.el6
@@ -663,10 +665,8 @@ LOAD AVERAGE: 0.00, 0.01, 0.00
        STATE: TASK_RUNNING (PANIC)
 
 crash&gt;</screen>
-    </example>
-    <para>
-      To exit the interactive prompt and terminate <application>crash</application>, type <command>exit</command>.
-    </para>
+      </example>
+    </section>
     <section id="s2-kdump-crash-log">
       <title>Displaying the Message Buffer</title>
       <indexterm>
@@ -846,6 +846,17 @@ ROOT: /    CWD: /root
         Type <command>help files</command> for more information on the command usage.
       </para>
     </section>
+    <section id="s2-kdump-crash-exit">
+      <title>Exiting the Utility</title>
+      <para>
+        To exit the interactive prompt and terminate <application>crash</application>, type <command>exit</command> or <command>q</command>.
+      </para>
+      <example id="ex-kdump-crash-exit">
+        <title>Exiting the <application>crash</application> utility</title>
+        <screen>crash&gt; <command>exit</command>
+~]#</screen>
+      </example>
+    </section>
   </section>
   <section id="s1-kdump-resources">
     <title>Additional Resources</title>