[deployment-guide/comm-rel: 273/727] Added the Configuring the kdump at First Boot section.

Jaromir Hradilek jhradile at fedoraproject.org
Tue Oct 19 12:47:31 UTC 2010


commit 44aa31cff6ed1f63f695936dbeeb9d9958800a41
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Fri Aug 6 14:20:19 2010 +0200

    Added the Configuring the kdump at First Boot section.

 en-US/The_kdump_Crash_Recovery_Service.xml |   24 ++++++++++++++++++++++++
 1 files changed, 24 insertions(+), 0 deletions(-)
---
diff --git a/en-US/The_kdump_Crash_Recovery_Service.xml b/en-US/The_kdump_Crash_Recovery_Service.xml
index 448189a..29d16c6 100644
--- a/en-US/The_kdump_Crash_Recovery_Service.xml
+++ b/en-US/The_kdump_Crash_Recovery_Service.xml
@@ -24,6 +24,30 @@
     <para>
       This section covers two common means of configuring the <systemitem class="service">kdump</systemitem> service: using the <application>Kernel Dump Configuration</application> graphical utility, and doing so manually on the command line. It also describes how to test the configuration to verify that everything works as expected.
     </para>
+    <section id="s2-kdump-configuration-firstboot">
+      <title>Configuring the <systemitem class="service">kdump</systemitem> at First Boot</title>
+      <para>
+        When the system boots for the first time, the <application>firstboot</application> application is launched to guide a user through the initial configuration of the freshly installed system. To configure <systemitem class="service">kdump</systemitem>, navigate to the <guilabel>Kdump</guilabel> section, and follow the instructions below.
+      </para>
+      <important>
+        <title>Important: Make Sure the System Has Enough Memory</title>
+        <para>
+          Unless the system has enough memory, this option will not be available. For the information on minimum memory requirements, refer to the <citetitle pubwork="section">Required minimums</citetitle> section of the <ulink url="http://www.redhat.com/rhel/compare/"><citetitle pubwork="webpage">Red Hat Enterprise Linux</citetitle> comparison chart</ulink>. Note that 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.
+        </para>
+      </important>
+      <section id="s3-kdump-configuration-firstboot-enable">
+        <title>Enabling the Service</title>
+        <para>
+          To start the <systemitem class="service">kdump</systemitem> daemon at boot time, select the <guilabel>Enable kdump?</guilabel> check box. This will enable the service for runlevels <literal>2</literal>, <literal>3</literal>, <literal>4</literal>, and <literal>5</literal>, and start it for the current session. Similarly, unselecting the check box will disable it for all runlevels and stop the service immediately.
+        </para>
+      </section>
+      <section id="s3-kdump-configuration-firstboot-memory">
+        <title>Configuring thr Memory Usage</title>
+        <para>
+          To configure the amount of memory that is reserved for the <systemitem>kdump</systemitem> kernel, click the up and down arrow buttons next to the <guilabel>Kdump Memory</guilabel> field to increase or decrease the value. Notice that the <guilabel>Usable System Memory</guilabel> field changes accordingly showing you the remaining memory that will be available to the system.
+        </para>
+      </section>
+    </section>
     <section id="s2-kdump-configuration-gui">
       <title>Using the <application>Kernel Dump Configuration</application> Utility</title>
       <indexterm>


More information about the docs-commits mailing list