From 29e57ce303571991bee5ab86f23ab749d701ecc9 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Thu, 13 Feb 2003 05:47:46 +0000
Subject: [PATCH] Add local ident OpenBSD mention that was missing in one
 place.

---
 doc/src/sgml/client-auth.sgml | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml
index 574fc50695..e7f61ef11d 100644
--- a/doc/src/sgml/client-auth.sgml
+++ b/doc/src/sgml/client-auth.sgml
@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/client-auth.sgml,v 1.44 2003/01/19 00:13:28 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/client-auth.sgml,v 1.45 2003/02/13 05:47:46 momjian Exp $
 -->
 
 <chapter id="client-authentication">
@@ -719,9 +719,9 @@ local   db1,db2,@demodbs  all                                       md5
     On systems supporting <symbol>SO_PEERCRED</symbol> requests for
     Unix-domain sockets (currently <systemitem
     class="osname">Linux</>, <systemitem class="osname">FreeBSD</>,
-    <systemitem class="osname">NetBSD</>, and <systemitem
-    class="osname">BSD/OS</>), ident authentication can also be applied
-    to local connections. In this case, no security risk is added by
+    <systemitem class="osname">NetBSD</>, <systemitem class=osname>OpenBSD</>, 
+    and <systemitem class="osname">BSD/OS</>), ident authentication can also 
+    be applied to local connections. In this case, no security risk is added by
     using ident authentication; indeed it is a preferable choice for
     local connections on such systems.
    </para>