[deployment-guide/comm-rel: 75/727] BZ614906

[Jaromir Hradilek]

commit 1a8aa3e075a1c28550b367ad85890b40f2ce67bc
Author: David O'Brien <davido at redhat.com>
Date:   Tue Jul 20 16:16:49 2010 +1000

    BZ614906

 en-US/SSSD.xml |   12 ++++++------
 1 files changed, 6 insertions(+), 6 deletions(-)
---
diff --git a/en-US/SSSD.xml b/en-US/SSSD.xml
index 3a96262..a4f4864 100644
--- a/en-US/SSSD.xml
+++ b/en-US/SSSD.xml
@@ -240,7 +240,7 @@ key10 = val10,val11
 
       <section id="sect-SSSD_User_Guide-Configuring_SSSD-Configuring_NSS">
         <title>Configuring NSS</title>
-        <para>SSSD provides a new NSS module, <systemitem>nss_sss</systemitem>, so that you can configure your system to use SSSD to retrieve user information. Edit the <filename>/etc/nsswitch.conf</filename> file for your system to use the <systemitem>sss</systemitem> name database. For example:</para>
+        <para>SSSD provides a new NSS module, <systemitem>sssd_nss</systemitem>, so that you can configure your system to use SSSD to retrieve user information. Edit the <filename>/etc/nsswitch.conf</filename> file for your system to use the <systemitem>sss</systemitem> name database. For example:</para>
 
 <programlisting>passwd: files sss
 group: files sss
@@ -412,11 +412,11 @@ simple_allow_users = user1, user2</screen>
     <itemizedlist>
       <listitem>
         <para>
-          <systemitem class="service">NSS</systemitem> &mdash; An NSS provider service that answers NSS requests from the <systemitem>nss_sss</systemitem> module.</para>
+          <systemitem class="service">NSS</systemitem> &mdash; An NSS provider service that answers NSS requests from the <systemitem>sssd_nss</systemitem> module.</para>
       </listitem>
       <listitem>
         <para>
-          <systemitem class="service">PAM</systemitem> &mdash; A PAM provider service that manages a PAM conversation through the <systemitem>pam_sss</systemitem> PAM module.</para>
+          <systemitem class="service">PAM</systemitem> &mdash; A PAM provider service that manages a PAM conversation through the <systemitem>sssd_pam</systemitem> PAM module.</para>
       </listitem>
       <listitem>
         <para>
@@ -462,14 +462,14 @@ simple_allow_users = user1, user2</screen>
               <option>enum_cache_timeout <type>(integer)</type>
               </option>
             </para>
-            <para>Specifies for how long (in seconds) <package>nss_sss</package> should cache enumerations (requests for information about all users).</para>
+            <para>Specifies for how long (in seconds) <package>sssd_nss</package> should cache enumerations (requests for information about all users).</para>
           </listitem>
           <listitem>
             <para>
               <option>entry_cache_nowait_percentage <type>(integer)</type>
               </option>
             </para>
-            <para>Specifies for how long <package>nss_sss</package> should return cached entries before initiating an out-of-band cache refresh (0 disables this feature).</para>
+            <para>Specifies for how long <package>sssd_nss</package> should return cached entries before initiating an out-of-band cache refresh (0 disables this feature).</para>
             <para>You can configure the entry cache to automatically update entries in the background if they are requested beyond a percentage of the <option>entry_cache_timeout</option> value for the domain.</para>
             <para>Valid values for this option are 0-99 and represent a percentage of the <option>entry_cache_timeout</option> value for each domain.</para>
           </listitem>
@@ -478,7 +478,7 @@ simple_allow_users = user1, user2</screen>
               <option>entry_negative_timeout <type>(integer)</type>
               </option>
             </para>
-            <para>Specifies for how long (in seconds) <package>nss_sss</package> should cache negative cache hits (that is, queries for invalid database entries, like nonexistent ones) before asking the back end again.</para>
+            <para>Specifies for how long (in seconds) <package>sssd_nss</package> should cache negative cache hits (that is, queries for invalid database entries, like nonexistent ones) before asking the back end again.</para>
           </listitem>
           <listitem>
             <para>