dgaudet 97/03/17 00:16:09
Modified: htdocs/manual/mod core.html
Log:
Document ScoreBoardfile. Note that PidFile is subject to security concerns
as well.
Revision Changes Path
1.41 +29 -1 apache/htdocs/manual/mod/core.html
Index: core.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/mod/core.html,v
retrieving revision 1.40
retrieving revision 1.41
diff -C3 -r1.40 -r1.41
*** core.html 1997/03/16 23:35:34 1.40
--- core.html 1997/03/17 08:16:07 1.41
***************
*** 51,56 ****
--- 51,57 ----
<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,883 ****
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>
<A name="port"><h2>Port directive</h2></A>
<!--%plaintext <?INDEX {\tt Port} directive> -->
--- 878,889 ----
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>
!
! 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 <?INDEX {\tt Port} directive> -->
***************
*** 1038,1043 ****
--- 1044,1071 ----
Access policy if both allow and require used. The parameter can be either
<em>'all'</em> or <em>'any'</em>.
+
+ <p><hr>
+
+ <A name="scoreboardfile"><h2>ScoreBoardFile directive</h2></A>
+ <!--%plaintext <?INDEX {\tt ScoreBoardFile} directive> -->
+ <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>
