[deployment-guide/comm-rel: 265/727] Corrected several typing errors.
Jaromir Hradilek
jhradile at fedoraproject.org
Tue Oct 19 12:46:51 UTC 2010
commit cb31b029b8f55c85273f58c84a4b2f6abd3afc39
Author: Jaromir Hradilek <jhradile at redhat.com>
Date: Wed Aug 4 16:13:32 2010 +0200
Corrected several typing errors.
en-US/The_kdump_Crash_Recovery_Service.xml | 22 +++++++++++-----------
1 files changed, 11 insertions(+), 11 deletions(-)
---
diff --git a/en-US/The_kdump_Crash_Recovery_Service.xml b/en-US/The_kdump_Crash_Recovery_Service.xml
index e972b94..b007406 100644
--- a/en-US/The_kdump_Crash_Recovery_Service.xml
+++ b/en-US/The_kdump_Crash_Recovery_Service.xml
@@ -153,7 +153,7 @@
</mediaobject>
</figure>
<para>
- To exclude the <guilabel>zero page</guilabel>, <guilabel>cache page</guilabel>, <guilabel>cache private</guilabel>, <guilabel>user data</guilabel>, or <guilabel>free page</guilabel> from the dump, select the check box next to the appropriate lable.
+ To exclude the <guilabel>zero page</guilabel>, <guilabel>cache page</guilabel>, <guilabel>cache private</guilabel>, <guilabel>user data</guilabel>, or <guilabel>free page</guilabel> from the dump, select the check box next to the appropriate label.
</para>
</section>
<section id="s3-kdump-configuration-gui-expert">
@@ -287,7 +287,7 @@ title Red Hat Enterprise Linux (2.6.32-54.el6.i686)
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:
+ 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 file system label, and UUID are all supported) accordingly. For example:
</para>
<screen>ext3 /dev/sda4
path /usr/local/cores</screen>
@@ -505,8 +505,8 @@ 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>
+ <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>
@@ -602,7 +602,7 @@ LOAD AVERAGE: 0.64, 0.27, 0.12
CPU: 0
STATE: TASK_RUNNING (PANIC)
-crash></screen>
+crash></screen>
</example>
<para>
To exit the interactive prompt and terminate <application>Crash</application>, type <command>exit</command>.
@@ -619,7 +619,7 @@ crash></screen>
</para>
<example id="ex-kdump-crash-log">
<title>Displaying the kernel message buffer</title>
- <screen>crash> <command>log</command>
+ <screen>crash> <command>log</command>
<emphasis>... several lines omitted ...</emphasis>
EIP is at sysrq_handle_crash+0x12/0x1b
EAX: 00000063 EBX: 00000063 ECX: c0a44e00 EDX: 00000000
@@ -661,7 +661,7 @@ CR2: 0000000000000000</screen>
</para>
<example id="ex-kdump-crash-backtrace">
<title>Displaying the kernel stack trace</title>
- <screen>crash> <command>bt</command>
+ <screen>crash> <command>bt</command>
PID: 5108 TASK: ee939980 CPU: 0 COMMAND: "bash"
#0 [eeabfde8] ia32_sysenter_target at c0465b5c
#1 [eeabfe3c] oops_end at c077209b
@@ -687,7 +687,7 @@ PID: 5108 TASK: ee939980 CPU: 0 COMMAND: "bash"
</para>
<example id="ex-kdump-crash-processes">
<title>Displaying status of processes in the system</title>
- <screen>crash> <command>ps</command>
+ <screen>crash> <command>ps</command>
PID PPID CPU TASK ST %MEM VSZ RSS COMM
0 0 0 c0958e20 RU 0.0 0 0 [swapper]
1 0 0 f6c40000 IN 0.1 2824 1384 init
@@ -717,7 +717,7 @@ PID: 5108 TASK: ee939980 CPU: 0 COMMAND: "bash"
</para>
<example id="ex-kdump-crash-memory">
<title>Displaying virtual memory information of the current context</title>
- <screen>crash> <command>vm</command>
+ <screen>crash> <command>vm</command>
PID: 5108 TASK: ee939980 CPU: 0 COMMAND: "bash"
MM PGD RSS TOTAL_VM
eea33540 ee90e000 1716k 5220k
@@ -760,7 +760,7 @@ eea68420 811d000 8122000 100073
</para>
<example id="ex-kdump-crash-files">
<title>Displaying information about open files of the current context</title>
- <screen>crash> <command>files</command>
+ <screen>crash> <command>files</command>
PID: 5108 TASK: ee939980 CPU: 0 COMMAND: "bash"
ROOT: / CWD: /root
FD FILE DENTRY INODE TYPE PATH
@@ -810,7 +810,7 @@ ROOT: / CWD: /root
<term><command>man kexec</command></term>
<listitem>
<para>
- The manual page for <command>kexec</command> containing the full documentaion on its usage.
+ The manual page for <command>kexec</command> containing the full documentation on its usage.
</para>
</listitem>
</varlistentry>
More information about the docs-commits
mailing list