[deployment-guide/comm-rel: 245/727] Extended the Enabling the Service subsection.

[Jaromir Hradilek]

commit b1ba06e21ab5c744469466cbe9c8e31b78828574
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Tue Aug 3 14:09:51 2010 +0200

    Extended the Enabling the Service subsection.

 en-US/The_kdump_Crash_Recovery_Service.xml |    9 ++++++++-
 1 files changed, 8 insertions(+), 1 deletions(-)
---
diff --git a/en-US/The_kdump_Crash_Recovery_Service.xml b/en-US/The_kdump_Crash_Recovery_Service.xml
index 973fa9e..c3ce82b 100644
--- a/en-US/The_kdump_Crash_Recovery_Service.xml
+++ b/en-US/The_kdump_Crash_Recovery_Service.xml
@@ -361,7 +361,14 @@ path /usr/local/cores</screen>
         </para>
         <screen>~]# <command>chkconfig kdump on</command></screen>
         <para>
-          This will enable the service for runlevels <literal>2</literal>, <literal>3</literal>, <literal>4</literal>, and <literal>5</literal>. Similarly, typing <command>chkconfig kdump off</command> will disable it for all runlevels. For more information on runlevels and configuring services in general, refer to <xref linkend="ch-Controlling_Access_to_Services" />.
+          This will enable the service for runlevels <literal>2</literal>, <literal>3</literal>, <literal>4</literal>, and <literal>5</literal>. Similarly, typing <command>chkconfig kdump off</command> will disable it for all runlevels. To start the service in the current session, use the following command:
+        </para>
+        <screen>~]# <command>service kdump start</command>
+No kdump initial ramdisk found.                            [WARNING]
+Rebuilding /boot/initrd-2.6.32-54.el6.x86_64kdump.img
+Starting kdump:                                            [  OK  ]</screen>
+        <para>
+          For more information on runlevels and configuring services in general, refer to <xref linkend="ch-Controlling_Access_to_Services" />.
         </para>
       </section>
     </section>