Update docs mentioning PAM doesn't work reading /etc/passwd because of

non-root.

Dhanaraj M

diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml
index 78c64046c40175e7c094a333c0281521a02f79d4..295326fcd1a7f3e67c2806810eaaf5f3ecd5929e 100644 (file)
--- a/doc/src/sgml/client-auth.sgml
+++ b/doc/src/sgml/client-auth.sgml
@@ -1079,11 +1079,10 @@ ldap[<replaceable>s</>]://<replaceable>servername</>[:<replaceable>port</>]/<rep
 
    <note>
     <para>
-     PAM does work authenticating against Unix system authentication
-     because the postgres server is started by a non-root user.  In order
-     to enable this functionality, the root user must provide additional
-     permissions to the postgres user (for reading
-     <filename>/etc/shadow</>).
+     If PAM is set up to read <filename>/etc/shadow</>, authentication
+     will fail because the PostgreSQL server is started by a non-root
+     user.  However, this is not an issue with LDAP or other authentication
+     methods.
     </para>
    </note>
   </sect2>