[deployment-guide: 69/185] added section Configuring Automatic Reporting to ABRT chapter

[Jaromir Hradilek]

commit 8303e2a613672b8eb8eacb8eef363796c0341fc6
Author: Martin Prpic <mprpic at redhat.com>
Date:   Wed Feb 2 14:08:17 2011 +0100

    added section Configuring Automatic Reporting to ABRT chapter

 en-US/Automatic_Bug_Reporting_Tool_ABRT.xml |   28 +++++++++++++++++++++++++++
 en-US/SSSD.xml                              |    5 +--
 2 files changed, 30 insertions(+), 3 deletions(-)
---
diff --git a/en-US/Automatic_Bug_Reporting_Tool_ABRT.xml b/en-US/Automatic_Bug_Reporting_Tool_ABRT.xml
index e928396..10bc3c4 100644
--- a/en-US/Automatic_Bug_Reporting_Tool_ABRT.xml
+++ b/en-US/Automatic_Bug_Reporting_Tool_ABRT.xml
@@ -828,4 +828,32 @@ ftp> quit
     </para>
     </section>
   </section>
+  <section id="configuring-automatic-reporting">
+    <title>Configuring Automatic Reporting</title>
+    <para>
+    <application>ABRT</application> can be configured to automatically report any detected issues or crashes. The following steps show how to enable this feature:
+    </para>
+    <orderedlist>
+      <listitem>
+        <para>
+          For each analyzer, change the list of reporters in the <filename>/etc/abrt/abrt.conf</filename> configuration file to include the <application>Logger</application> plugin only:
+        </para>
+        <screen>
+[ AnalyzerActionsAndReporters ]
+Kerneloops = Logger
+CCpp = Logger
+Python = Logger
+        </screen>
+      </listitem>
+      <listitem>
+        <para>
+          In the configuration files corresponding to each analyzer plugin (that is, <filename>/etc/abrt/plugins/CCpp.conf</filename>, <filename>/etc/abrt/plugins/Kerneloops.conf</filename> and <filename>/etc/abrt/plugins/Python.conf</filename>), add the following line:
+        </para>
+        <screen>AutoReportUIDs = <replaceable>&lt;USERNAME&gt;</replaceable></screen>
+        <para>
+          where <replaceable>&lt;USERNAME&gt;</replaceable> represents a user to which the detected crashes and issues will be reported to. You can specify multiple users by separating them with a comma (<literal>,</literal>).
+        </para>
+      </listitem>
+    </orderedlist>  
+  </section>
 </chapter>
diff --git a/en-US/SSSD.xml b/en-US/SSSD.xml
index 4c371a4..2d53026 100644
--- a/en-US/SSSD.xml
+++ b/en-US/SSSD.xml
@@ -927,7 +927,7 @@ ldap_tls_cacert = /etc/pki/tls/certs/ca-bundle.crt
         <para>If you wish to use an IP address in the <option>ldap_uri</option> option instead of the server name, for example, if <systemitem class="protocol">GSSAPI</systemitem> is used to avoid time consuming <systemitem class="protocol">DNS</systemitem> lookups, the <systemitem class="protocol">TSL</systemitem>/<systemitem class="protocol">SSL</systemitem> setup might fail. This is due to the fact that <systemitem class="protocol">TSL</systemitem>/<systemitem class="protocol">SSL</systemitem> certificates contain the server name only. However, a special field in the certificate, called <emphasis>Subject Alternative Name</emphasis> (<option>subjectAltName</option>), can be used to additionally set the IP address of the server.</para>
 
         <para>The following steps show how to create a certificate with a Subject Alternative Name being the IP address of your server:</para>
-        <itemizedlist>
+        <orderedlist>
           <listitem>
             <para>
              Using your command line, execute the following command to convert an existing certificate (previously signed by the <parameter>key.pem</parameter> key) into a certificate request:
@@ -997,7 +997,7 @@ ldap_tls_cacert = /etc/pki/tls/certs/ca-bundle.crt
               Lastly, copy the private key block from the <filename>old_cert.pem</filename> file into the new_<filename>cert.pem</filename> file to keep all relevant information in one file.
             </para>
           </listitem>
-        </itemizedlist>
+        </orderedlist>
         <para>
           When creating a certificate through the <application>certutil</application> utility provided by the <package>nss-utils</package> package, note that <application>certutil</application> supports <systemitem class="protocol">DNS</systemitem> subject alternative names for certificate creation only.
         </para>
@@ -1080,7 +1080,6 @@ uid=500(f12server) gid=500(f12server) groups=500(f12server),510(f12tester)
           </itemizedlist>
         </para>
       </formalpara>
-
     </section>
 
     <section id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain">