dgaudet 97/04/24 14:08:12
Modified: htdocs/manual stopping.html
Log:
Document scoreboardfile lameness.
Revision Changes Path
1.2 +9 -6 apache/htdocs/manual/stopping.html
Index: stopping.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/stopping.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C3 -r1.1 -r1.2
*** stopping.html 1997/04/23 02:40:50 1.1
--- stopping.html 1997/04/24 21:08:11 1.2
***************
*** 64,69 ****
--- 64,74 ----
replaces it with a child from the new <i>generation</i> of the
configuration, which begins serving new requests immediately.
+ <p>Architectures that use an on disk <a
+ href="mod/core.html#scoreboardfile">ScoreBoardFile</a> are not supported
+ on graceful restarts. See the ScoreBoardFile documentation for a method
+ to determine if your architecture uses it.
+
<p>This code is designed to always respect the
<a href="mod/core.html#maxclients">MaxClients</a>,
<a href="mod/core.html#minspareservers">MinSpareServers</a>,
***************
*** 109,120 ****
<p>Architectures that use an on disk <a
href="mod/core.html#scoreboardfile">ScoreBoardFile</a> have the potential
! to lose track of a child during graceful restart (you'll see an <a
! href="mod/core.html#errorlog">ErrorLog</a> message saying something about
! a <i>long lost child</i>). The ScoreBoardFile directive explains how
! to figure out if your server uses a file, and possibly how to avoid it.
! There is also the potential that the scoreboard will be corrupted during
! any signalling, but this only has bad effects on graceful restart.
<p><code>NEXT</code> and <code>MACHTEN</code> have small race conditions
which can cause a restart/die signal to be lost, but should not cause the
--- 114,123 ----
<p>Architectures that use an on disk <a
href="mod/core.html#scoreboardfile">ScoreBoardFile</a> have the potential
! to corrupt their scoreboards whenever a signal is received. It is
! possible for the server to forget about some children when this happens.
! See the ScoreBoardFile documentation for a method to determine if your
! architecture uses it.
<p><code>NEXT</code> and <code>MACHTEN</code> have small race conditions
which can cause a restart/die signal to be lost, but should not cause the
Modified: htdocs/manual stopping.html
Log:
Document scoreboardfile lameness.
Revision Changes Path
1.2 +9 -6 apache/htdocs/manual/stopping.html
Index: stopping.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/stopping.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -C3 -r1.1 -r1.2
*** stopping.html 1997/04/23 02:40:50 1.1
--- stopping.html 1997/04/24 21:08:11 1.2
***************
*** 64,69 ****
--- 64,74 ----
replaces it with a child from the new <i>generation</i> of the
configuration, which begins serving new requests immediately.
+ <p>Architectures that use an on disk <a
+ href="mod/core.html#scoreboardfile">ScoreBoardFile</a> are not supported
+ on graceful restarts. See the ScoreBoardFile documentation for a method
+ to determine if your architecture uses it.
+
<p>This code is designed to always respect the
<a href="mod/core.html#maxclients">MaxClients</a>,
<a href="mod/core.html#minspareservers">MinSpareServers</a>,
***************
*** 109,120 ****
<p>Architectures that use an on disk <a
href="mod/core.html#scoreboardfile">ScoreBoardFile</a> have the potential
! to lose track of a child during graceful restart (you'll see an <a
! href="mod/core.html#errorlog">ErrorLog</a> message saying something about
! a <i>long lost child</i>). The ScoreBoardFile directive explains how
! to figure out if your server uses a file, and possibly how to avoid it.
! There is also the potential that the scoreboard will be corrupted during
! any signalling, but this only has bad effects on graceful restart.
<p><code>NEXT</code> and <code>MACHTEN</code> have small race conditions
which can cause a restart/die signal to be lost, but should not cause the
--- 114,123 ----
<p>Architectures that use an on disk <a
href="mod/core.html#scoreboardfile">ScoreBoardFile</a> have the potential
! to corrupt their scoreboards whenever a signal is received. It is
! possible for the server to forget about some children when this happens.
! See the ScoreBoardFile documentation for a method to determine if your
! architecture uses it.
<p><code>NEXT</code> and <code>MACHTEN</code> have small race conditions
which can cause a restart/die signal to be lost, but should not cause the