Document ScoreBoardfile. Note that PidFile is subject to security concerns

as well.
Reviewed by:
Submitted by:
Obtained from:

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@77729 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/mod/core.html b/docs/manual/mod/core.html
index cc7ff8b8f96f7ba1a774fba7cbfa4cb755a160b8..6cd78d1f2873bbc825b0ef2a04e1a826ae12e6b9 100644 (file)
--- a/docs/manual/mod/core.html
+++ b/docs/manual/mod/core.html
@@ -51,6 +51,7 @@ always available.
 <li><A HREF="#rlimitmem">RLimitMEM</A>
 <li><A HREF="#rlimitnproc">RLimitNPROC</A>
 <li><A HREF="#satisfy">Satisfy</A>
+<li><A HREF="#scoreboardfile">ScoreBoardFile</A>
 <li><A HREF="#sendbuffersize">SendBufferSize</A>
 <li><A HREF="#serveradmin">ServerAdmin</A>
 <li><A HREF="#serveralias">ServerAlias</A>
@@ -877,7 +878,12 @@ The PidFile is only used in <A HREF="#servertype">standalone</A> mode.<p>
 It is often useful to be able to send the server a signal, so that it closes
 and then reopens its <A HREF="#errorlog">ErrorLog</A> and TransferLog, and
 re-reads its configuration files. This is done by sending a SIGHUP (kill -1)
-signal to the process id listed in the PidFile.<p><hr>
+signal to the process id listed in the PidFile.<p>
+
+The PidFile is subject to the same warnings about log file placement and
+<a href="../misc/security_tips.html">security</a>.
+
+<p><hr>
 
 <A name="port"><h2>Port directive</h2></A>
 <!--%plaintext &lt;?INDEX {\tt Port} directive&gt; -->
@@ -1041,6 +1047,28 @@ Access policy if both allow and require used. The parameter can be either
 
 <p><hr>
 
+<A name="scoreboardfile"><h2>ScoreBoardFile directive</h2></A>
+<!--%plaintext &lt;?INDEX {\tt ScoreBoardFile} directive&gt; -->
+<strong>Syntax:</strong> ScoreBoardFile <em>filename</em><br>
+<strong>Default:</strong> <code>ScoreBoardFile logs/apache_status</code><br>
+<strong>Context:</strong> server config<br>
+<strong>Status:</strong> core<p>
+
+The ScoreBoardFile directive is required on some architectures to place
+a file that the server will use to communicate between its children and
+the parent.  The easiest way to find out if your architecture requires
+a scoreboard file is to run Apache and see if it creates the file named
+by the directive.  If your architecture requires it then you must ensure
+that this file is not used at the same time by more than one invocation
+of Apache.<p>
+
+If you have to use a ScoreBoardFile then you may see improved speed by
+placing it on a RAM disk.  But be careful that you heed the same warnings
+about log file placement and
+<a href="../misc/security_tips.html">security</a>.
+
+<p><hr>
+
 <A name="sendbuffersize"><h2>SendBufferSize directive</h2></A>
 <!--%plaintext &lt;?INDEX {\tt SendBufferSize} directive&gt; -->
 <strong>Syntax:</strong> SendBufferSize <em>bytes</em><br>