[deployment-guide/comm-rel: 218/727] Polished the section a bit.
Jaromir Hradilek
jhradile at fedoraproject.org
Tue Oct 19 12:42:45 UTC 2010
commit 524bcc97f1c497891f2315e10410c1bff3bcfd43
Author: Jaromir Hradilek <jhradile at redhat.com>
Date: Mon Aug 2 15:07:43 2010 +0200
Polished the section a bit.
en-US/The_kdump_Crash_Recovery_Service.xml | 12 ++++++------
1 files changed, 6 insertions(+), 6 deletions(-)
---
diff --git a/en-US/The_kdump_Crash_Recovery_Service.xml b/en-US/The_kdump_Crash_Recovery_Service.xml
index 3f768ab..1f636a6 100644
--- a/en-US/The_kdump_Crash_Recovery_Service.xml
+++ b/en-US/The_kdump_Crash_Recovery_Service.xml
@@ -154,14 +154,14 @@
<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 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:
+ 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><size></replaceable>M</option> parameter to the list of kernel options as shown in <xref linkend="ex-kdump-configuration-cli-memory-grub" />.
+ 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 such as <application>vi</application> or <application>nano</application>, and add the <option>crashkernel=<replaceable><size></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>
@@ -194,7 +194,7 @@ title Red Hat Enterprise Linux (2.6.32-54.el6.x86_64)
<section id="s3-kdump-configuration-cli-target">
<title>Configuring the Target Type</title>
<para>
- When a kernel crash is captured, the core dump can be either stored as a file in a local file system, written directly to a device, or sent over a network using the NFS (Network File System) or SSH (Secure Shell) protocol. Note that only one of these options can be set in the <filename>/etc/kdump.conf</filename> at the moment. The default option is to store the <filename>vmcore</filename> file in the <filename class="directory">/var/crash/</filename> directory of the local file system.
+ When a kernel crash is captured, the core dump can be either stored as a file in a local file system, written directly to a device, or sent over a network using the NFS (Network File System) or SSH (Secure Shell) protocol. Note that only one of these options can be set at the moment. The default option is to store the <filename>vmcore</filename> file in the <filename class="directory">/var/crash/</filename> directory of the local file system. To change this, 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.
</para>
<para>
To change the local directory in which the core dump is to be saved, remove the hash sign (<quote>#</quote>) from the beginning of the <literal>#path /var/crash</literal> line, and replace the value with a desired directory path. Optionally, if you wish to write the file to a different partition, follow the same procedure with the <literal>#ext4 /dev/sda3</literal> line as well, and change both the file system type and the device (a device name, a filesystem label, and UUID are all supported) accordingly. For example:
@@ -223,7 +223,7 @@ path /usr/local/cores</screen>
To reduce the size of the <filename>vmcore</filename> dump file, <systemitem class="service">kdump</systemitem> allows you to specify an external application (that is, a core collector) to compress the data, and optionally leave out all irrelevant information. Currently, the only fully supported core collector is <command>makedumpfile</command>.
</para>
<para>
- To enable the core collector, open the <filename>/etc/kdump.conf</filename> configuration file in a text editor of your choice, remove the hash sign (<quote>#</quote>) from the beginning of the <literal>#core_collector makedumpfile -c --message-level 1 -d 31</literal> line, and edit the command line options as described below.
+ To enable the core collector, open the <filename>/etc/kdump.conf</filename> configuration file in a text editor such as <application>vi</application> or <application>nano</application>, remove the hash sign (<quote>#</quote>) from the beginning of the <literal>#core_collector makedumpfile -c --message-level 1 -d 31</literal> line, and edit the command line options as described below.
</para>
<para>
To enable the dump file compression, add the <option>-c</option> parameter. For example:
@@ -234,10 +234,10 @@ path /usr/local/cores</screen>
</para>
<screen>core_collector makedumpfile -d 17 -c</screen>
<para>
- Refer to the <command>makedumpfile</command> manual page for a complete list of available options.
+ Refer to the manual page for <command>makedumpfile</command> for a complete list of available options.
</para>
<table id="table-kdump-configuration-cli-filtering-makedumpfile">
- <title>Available filtering levels</title>
+ <title>Supported <command>makedumpfile</command> filtering levels</title>
<tgroup cols="2">
<colspec colname="type" colnum="1" />
<colspec colname="value" colnum="2" />
More information about the docs-commits
mailing list