[deployment-guide/comm-rel: 211/727] Wrote the Configuring the Target Type section.

[Jaromir Hradilek]

commit 6c4b53fb3c29e9433be6533ff96ead2f2feae4f9
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Sat Jul 31 02:17:37 2010 +0200

    Wrote the Configuring the Target Type section.

 en-US/The_kdump_Crash_Recovery_Service.xml |   28 +++++++++++++++++++++++++++-
 1 files changed, 27 insertions(+), 1 deletions(-)
---
diff --git a/en-US/The_kdump_Crash_Recovery_Service.xml b/en-US/The_kdump_Crash_Recovery_Service.xml
index 6e4e50b..ace894e 100644
--- a/en-US/The_kdump_Crash_Recovery_Service.xml
+++ b/en-US/The_kdump_Crash_Recovery_Service.xml
@@ -69,7 +69,7 @@
       <section id="s3-kdump-configuration-gui-target">
         <title>The <guilabel>Target Settings</guilabel> Tab</title>
         <para>
-          The <guilabel>Target Settings</guilabel> tab enables you to specify the target location for the <filename>vmcore</filename> dump. It can be either stored as a file in the local file system, written directly to a device, or sent over a network using the NFS (Network File System) or SSH (Secure Shell; see <xref linkend="ch-OpenSSH" /> for more information on how to configure the SSH server) protocol.
+          The <guilabel>Target Settings</guilabel> tab enables you to specify the target location for the <filename>vmcore</filename> dump. It 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; see <xref linkend="ch-OpenSSH" /> for more information on how to configure an SSH server) protocol.
         </para>
         <figure id="fig-kdump-kernel_dump_configuration-target_settings">
           <title><guilabel>Target Settings</guilabel></title>
@@ -158,6 +158,32 @@
       </para>
       <screen>~]$ <command>su -</command>
 Password:</screen>
+      <section id="s3-kdump-configuration-cli-target">
+        <title>Configuring the Target Type</title>
+        <para>
+          When the 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.
+        </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:
+        </para>
+        <screen>ext3 /dev/sda4
+path /usr/local/cores</screen>
+        <para>
+          To write the dump directly to a device, remove the hash sign (<quote>#</quote>) from the beginning of the <literal>#raw /dev/sda5</literal> line, and replace the value with a desired device name. For example:
+        </para>
+        <screen>raw /dev/sdb1</screen>
+        <para>
+          To store the dump to a remote machine using the NFS protocol, remove the hash sign (<quote>#</quote>) from the beginning of the <literal>#net my.server.com:/export/tmp</literal> line, and replace the value with a valid hostname and directory path. For example:
+        </para>
+        <screen>net penguin.example.com:/export/cores</screen>
+        <para>
+          To store the dump to a remote machine using the SSH protocol, remove the hash sign (<quote>#</quote>) from the beginning of the <literal>#net user at my.server.com</literal>, and replace the value with a valid username and hostname. For example:
+        </para>
+        <screen>net john at penguin.example.com</screen>
+        <para>
+          Refer to <xref linkend="ch-OpenSSH" /> for information on how to configure an SSH server, and how to set up a key-based authentication.
+        </para>
+      </section>
       <section id="s3-kdump-configuration-cli-enable">
         <title>Enabling the Service</title>
         <para>