[deployment-guide/comm-rel: 554/727] modified the ABRT chapter

[Jaromir Hradilek]

commit ee10d9d4c530c15ae68224ab6992f0d5bbb55b5e
Author: Martin Prpic <mprpic at redhat.com>
Date:   Thu Sep 2 00:00:12 2010 +0200

    modified the ABRT chapter

 en-US/ABRT.xml |   26 ++++++++++----------------
 1 files changed, 10 insertions(+), 16 deletions(-)
---
diff --git a/en-US/ABRT.xml b/en-US/ABRT.xml
index 31bf220..e3fa0b2 100644
--- a/en-US/ABRT.xml
+++ b/en-US/ABRT.xml
@@ -487,7 +487,13 @@ Caching debuginfo:
 usr/lib/debug/.build-id/3d/b29c9308cb276431ce8854a2d88cf83518afc6.debug
 Caching debuginfo:
 usr/lib/debug/.build-id/a3/86884285365c8288e4e761ec034fafaa1daee1.debug
-...
+&#x22ee;
+Download 7/7: zlib-debuginfo-1.2.3-23.fc12.x86_64
+Unpacking: zlib-debuginfo-1.2.3-23.fc12.x86_64.rpm
+Caching debuginfo:
+usr/lib/debug/.build-id/f7/933750da80f555321576e72b375caf7a3cc075.debug
+All needed debuginfos are present
+Generating backtrace
       </screen>
       <para>
         This process is performed by the <application>/usr/bin/abrt-debuginfo-install</application> shell script. This script uses a temporary directory (e.g. <filename>/var/run/abrt/tmp-29177-1283344373</filename>) for its operations. Normally, this directory is removed when <application>abrt-debuginfo-install</application> exits.
@@ -507,7 +513,7 @@ debug=true
 keep_tmp=true
         </screen>
         <para>
-        The first parameter instructs <application>abrt-debuginfo-install</application> to be verbose, the second parameter instructs <application>abrt-debuginfo-install</application> to not delete the <filename>/var/run/abrt/tmp-NNN-NNN</filename> directory. You can examine the log files in this directory to provide you with useful error messages.
+        The first parameter instructs <application>abrt-debuginfo-install</application> to be verbose, the second parameter instructs <application>abrt-debuginfo-install</application> to not delete the <filename>/var/run/abrt/tmp-NNN-NNN</filename> directory. You can examine the log files in this directory, they may contain useful error messages.
         </para>
         <para>
         <application>abrt-debuginfo-install</application> uses <application>yum</application> and <application>yumdownloader</application> to handle the <package>debuginfo</package> packages. In order to quickly check that your <application>yum</application> configuration does not cause any problems which prevent <application>abrt-debuginfo-install</application> from working properly, change to the <filename>/tmp</filename> directory and run the following commands, as root:
@@ -517,19 +523,7 @@ tmp]# yum --enablerepo=*debuginfo* --quiet provides /usr/bin/true
 tmp]# yumdownloader --enablerepo=*debuginfo* --quiet coreutils
         </screen>
         <para>
-        Both of these commands should complete successfully, with no error messages. The second command should download the <filename>coreutils-*.rpm</filename> file. If any error messages appear, check your <application>yum</application> configuration in the files in the <filename>/etc/yum.repos.d/*</filename> directory and the <filename>/etc/yum/*</filename> directory. If any of these commands hang, check that you do not have another instance of <application>yum</application> running, and that your network connection is working properly.
-        </para>
-        <para>
-        The following is the end of a typical output seen in the <guilabel>Generating backtrace</guilabel> window:
-        <screen>
-...
-Download 7/7: zlib-debuginfo-1.2.3-23.fc12.x86_64
-Unpacking: zlib-debuginfo-1.2.3-23.fc12.x86_64.rpm
-Caching debuginfo:
-usr/lib/debug/.build-id/f7/933750da80f555321576e72b375caf7a3cc075.debug
-All needed debuginfos are present
-Generating backtrace
-        </screen>
+        Both of these commands should complete successfully, with no error messages. The second command should download the <filename>coreutils-*.rpm</filename> file. If any error messages appear, check your <application>yum</application> configuration files in the <filename>/etc/yum.repos.d/*</filename> directory and the <filename>/etc/yum/*</filename> directory. If any of these commands hang, check that you do not have another instance of <application>yum</application> running, and that your network connection is working properly.
         </para>
     </section>
   </section>
@@ -556,7 +550,7 @@ Generating backtrace
    Crash Time : Tue 20 Jul 2010 03:22:00 PM CEST
    Crash Count: 1
 </screen>
-      <para>This output contains basic information for every crash. The <computeroutput>UID:</computeroutput> field shows the ID of the user which ran the program that caused the crash. It is useful when <command>abrt-cli</command> is executed with superuser privileges and it lists crashes from all users. The <computeroutput>Package</computeroutput> field shows the name and version of the &MAJOROS; package that contains the program, and the <computeroutput>Executable</computeroutput> field shows the location of the binary or script that crashed. The <computeroutput>Crash Count</computeroutput> field indicates how many times the same crash happened.</para>
+      <para>This output contains basic information for every crash. The <computeroutput>UID:</computeroutput> field shows the ID of the user which ran the program that caused the crash. The <computeroutput>Package</computeroutput> field shows the name and version of the &MAJOROS; package that contains the program, and the <computeroutput>Executable</computeroutput> field shows the location of the binary or script that crashed. The <computeroutput>Crash Count</computeroutput> field indicates how many times the same crash happened.</para>
     </section>
     <section>
       <title>Reporting Crashes</title>