From: Bruce Momjian <bruce@momjian.us>
Date: Tue, 11 Apr 2006 19:46:48 +0000 (+0000)
Subject: More FreeBSD jail wording improvements.
X-Git-Tag: REL8_1_4~41
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=e860973aed266399680ddc6637d36029ceb3c15f;p=postgresql

More FreeBSD jail wording improvements.
---

diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 9cee668edf..90b2a1aa5c 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.357.2.2 2006/04/11 19:28:03 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.357.2.3 2006/04/11 19:46:48 momjian Exp $
 -->
 
 <chapter Id="runtime">
@@ -770,9 +770,9 @@ options "SEMMNS=240"
         If running in FreeBSD jails by enabling <application>sysconf</>'s
         <literal>security.jail.sysvipc_allowed</>, <application>postmaster</>s
         running in different jails should be run by different operating system
-        users.  This improves security because it prevents one jail from
-        interfering with shared memory or semaphores in another, and it
-        allows the PostgreSQL IPC cleanup code to function properly.  
+        users.  This improves security because it prevents non-root users
+        from interfering with shared memory or semaphores in a different jail,
+        and it allows the PostgreSQL IPC cleanup code to function properly.
         (In FreeBSD 6.0 and later the IPC cleanup code doesn't properly detect
         processes in other jails, preventing the running of postmasters on the
         same port in different jails.)