Update SysV parameter configuration documentation for FreeBSD.

FreeBSD hasn't made any use of kern.ipc.semmap since 1.1, and newer
releases reject attempts to set it altogether; so stop recommending
that it be adjusted.  Per bug #11161.

Back-patch to all supported branches.  Before 9.3, also incorporate
commit 7a42dff47, which touches the same text and for some reason
was not back-patched at the time.

1 files changed, 6 insertions, 4 deletions

diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index a82563b50d2..8bfb96a50bd 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -745,14 +745,13 @@ psql: could not connect to server: No such file or directory
 <screen>
 <prompt>#</prompt> <userinput>sysctl kern.ipc.shmall=32768</userinput>
 <prompt>#</prompt> <userinput>sysctl kern.ipc.shmmax=134217728</userinput>
-<prompt>#</prompt> <userinput>sysctl kern.ipc.semmap=256</userinput>
 </screen>
-        To have these settings persist over reboots, modify
+        To make these settings persist over reboots, modify
         <filename>/etc/sysctl.conf</filename>.
        </para>
 
        <para>
-        The remaining semaphore settings are read-only as far as
+        These semaphore-related settings are read-only as far as
         <command>sysctl</command> is concerned, but can be set in
         <filename>/boot/loader.conf</filename>:
 <programlisting>
@@ -761,7 +760,10 @@ kern.ipc.semmns=512
 kern.ipc.semmnu=256
 </programlisting>
         After modifying these values a reboot is required for the new
-        settings to take affect.
+        settings to take effect.
+        (Note: FreeBSD does not use <varname>SEMMAP</>.  Older versions
+        would accept but ignore a setting for <literal>kern.ipc.semmap</>;
+        newer versions reject it altogether.)
        </para>
 
        <para>