[deployment-guide/comm-rel: 216/727] Added the Configuring the Memory Usage subsection.

Jaromir Hradilek jhradile at fedoraproject.org
Tue Oct 19 12:42:35 UTC 2010


commit 4d9567965c57c99dfec516e6cfc14f67399067f0
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Mon Aug 2 13:45:06 2010 +0200

    Added the Configuring the Memory Usage subsection.

 en-US/The_kdump_Crash_Recovery_Service.xml |   37 ++++++++++++++++++++++++++-
 1 files changed, 35 insertions(+), 2 deletions(-)
---
diff --git a/en-US/The_kdump_Crash_Recovery_Service.xml b/en-US/The_kdump_Crash_Recovery_Service.xml
index b7873c0..479ead5 100644
--- a/en-US/The_kdump_Crash_Recovery_Service.xml
+++ b/en-US/The_kdump_Crash_Recovery_Service.xml
@@ -20,7 +20,7 @@
         The utility allows you to configure <systemitem class="service">kdump</systemitem> as well as to enable or disable starting the service at boot time. When you are done, click <guibutton>Apply</guibutton> to save the changes. The system reboot will be requested, and unless you are already authenticated, you will be prompted to enter the superuser password.
       </para>
       <important>
-        <title>Important: Make Sure Your System Has Enough Memory</title>
+        <title>Important: Make Sure the System Has Enough Memory</title>
         <para>
           Unless the system has enough memory, the utility will not start, and you will be presented with the following error message:
         </para>
@@ -154,10 +154,43 @@
     <section id="s2-kdump-configuration-cli">
       <title>Configuring <systemitem class="service">kdump</systemitem> on the Command Line</title>
       <para>
-        To configure the <systemitem class="service">kdump</systemitem> service on the command line, open the <filename>/etc/kdump.conf</filename> configuration file in a texteditor such as <application>vi</application> or <application>nano</application>, and edit the options as described below. Note that to perform actions described in this section, you have to be logged in as a superuser:
+        To configure the <systemitem class="service">kdump</systemitem> service on the command line, open the <filename>/etc/kdump.conf</filename> configuration file in a text editor such as <application>vi</application> or <application>nano</application>, and edit the options as described below. Note that to perform actions described in this section, you have to be logged in as a superuser:
       </para>
       <screen>~]$ <command>su -</command>
 Password:</screen>
+      <section id="s3-kdump-configuration-cli-memory">
+        <title>Configuring the Memory Usage</title>
+        <para>
+          To configure the amount of memory that is reserved for the <systemitem>kdump</systemitem> kernel, open the <filename>/boot/grub/grub.conf</filename> file in a text editor of your choice, and add the <option>crashkernel=<replaceable>&lt;size&gt;</replaceable>M</option> parameter to the list of kernel options as shown in <xref linkend="ex-kdump-configuration-cli-memory-grub" />.
+        </para>
+        <example id="ex-kdump-configuration-cli-memory-grub">
+          <title>A sample <filename>/boot/grub/grub.conf</filename> file</title>
+          <screen># grub.conf generated by anaconda
+#
+# Note that you do not have to rerun grub after making changes to this file
+# NOTICE:  You have a /boot partition.  This means that
+#          all kernel and initrd paths are relative to /boot/, eg.
+#          root (hd0,0)
+#          kernel /vmlinuz-version ro root=/dev/sda3
+#          initrd /initrd
+#boot=/dev/sda
+default=0
+timeout=5
+splashimage=(hd0,0)/grub/splash.xpm.gz
+hiddenmenu
+title Red Hat Enterprise Linux (2.6.32-54.el6.x86_64)
+        root (hd0,0)
+        kernel /boot/vmlinuz-2.6.32-54.el6.x86_64 root=/dev/sda3 ro crashkernel=128M
+        initrd /initramfs-2.6.32-54.el6.x86_64.img
+</screen>
+        </example>
+        <important>
+          <title>Important: Make Sure the System Has Enough Memory</title>
+          <para>
+            When the <systemitem class="service">kdump</systemitem> crash recovery is enabled, the minimum memory requirements increase by the amount of memory reserved for it. This value is determined by a user, and defaults to 128 MB, as lower values proved to be unreliable. For more information on minimum memory requirements for &MAJOROSVER;, refer to the <citetitle pubwork="section">Required minimums</citetitle> section of the <ulink url="http://www.redhat.com/rhel/compare/">Red Hat Enterprise Linux comparison chart</ulink>.
+          </para>
+        </important>
+      </section>
       <section id="s3-kdump-configuration-cli-target">
         <title>Configuring the Target Type</title>
         <para>


More information about the docs-commits mailing list