dgaudet 97/04/24 17:07:03
Modified: htdocs/manual index.html invoking.html stopping.html
htdocs/manual/mod mod_proxy.html
Log:
Point things at the stopping/restarting document.
Revision Changes Path
1.9 +1 -0 apache/htdocs/manual/index.html
Index: index.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/index.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -C3 -r1.8 -r1.9
*** index.html 1997/02/22 17:22:32 1.8
--- index.html 1997/04/25 00:06:59 1.9
***************
*** 26,31 ****
--- 26,32 ----
<ul>
<li><A HREF="install.html">Compiling and Installing Apache</A>
<li><A HREF="invoking.html">Starting Apache</A>
+ <li><A HREF="stopping.html">Stopping or Restarting Apache</A>
<li><A HREF="mod/directives.html">Apache run-time configuration directives</A>
<li><A HREF="mod/">Apache modules</A>
<li><A HREF="handler.html">Apache's handler use</A>
1.9 +3 -2 apache/htdocs/manual/invoking.html
Index: invoking.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/invoking.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -C3 -r1.8 -r1.9
*** invoking.html 1997/02/03 02:01:09 1.8
--- invoking.html 1997/04/25 00:06:59 1.9
***************
*** 92,99 ****
the file <code>logs/httpd.pid</code>. This filename can be changed with the
<A HREF="mod/core.html#pidfile">PidFile</A> directive. The process-id is for
use by the administrator in restarting and terminating the daemon;
! A HUP signal causes the daemon to re-read its configuration files and
! a TERM signal causes it to die gracefully.
<p>
If the process dies (or is killed) abnormally, then it will be necessary to
kill the children httpd processes.
--- 92,100 ----
the file <code>logs/httpd.pid</code>. This filename can be changed with the
<A HREF="mod/core.html#pidfile">PidFile</A> directive. The process-id is for
use by the administrator in restarting and terminating the daemon;
! A HUP or USR1 signal causes the daemon to re-read its configuration files and
! a TERM signal causes it to die gracefully. For more information
! see the <a href="stopping.html">Stopping and Restarting</a> page.
<p>
If the process dies (or is killed) abnormally, then it will be necessary to
kill the children httpd processes.
1.3 +7 -6 apache/htdocs/manual/stopping.html
Index: stopping.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/stopping.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -C3 -r1.2 -r1.3
*** stopping.html 1997/04/24 21:08:11 1.2
--- stopping.html 1997/04/25 00:06:59 1.3
***************
*** 57,62 ****
--- 57,67 ----
<p><b>Note:</b> prior to release 1.2b9 this code is quite unstable and
shouldn't be used at all.
+ <p><b>Note:</b> 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 a file.
+
<p>The <code>USR1</code> signal causes the parent process to <i>advise</i>
the children to exit after their current request (or to exit immediately
if they're not serving anything). The parent re-reads its configuration
***************
*** 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>,
--- 69,74 ----
***************
*** 114,120 ****
<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.
--- 114,121 ----
<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 (by the
! parent or children). 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.
1.18 +1 -1 apache/htdocs/manual/mod/mod_proxy.html
Index: mod_proxy.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_proxy.html,v
retrieving revision 1.17
retrieving revision 1.18
diff -C3 -r1.17 -r1.18
*** mod_proxy.html 1997/04/21 03:12:06 1.17
--- mod_proxy.html 1997/04/25 00:07:02 1.18
***************
*** 199,205 ****
<strong>Context:</strong> server config<br>
<strong>Status:</strong> Base<br>
<strong>Module:</strong> mod_proxy<br>
! <strong>Compatibility:</strong> CacheLastModified is only available in
Apache 1.1 and later.<p>
If the origin HTTP server did not supply an expiry date for the
--- 199,205 ----
<strong>Context:</strong> server config<br>
<strong>Status:</strong> Base<br>
<strong>Module:</strong> mod_proxy<br>
! <strong>Compatibility:</strong> CacheLastModifiedFactor is only available in
Apache 1.1 and later.<p>
If the origin HTTP server did not supply an expiry date for the
Modified: htdocs/manual index.html invoking.html stopping.html
htdocs/manual/mod mod_proxy.html
Log:
Point things at the stopping/restarting document.
Revision Changes Path
1.9 +1 -0 apache/htdocs/manual/index.html
Index: index.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/index.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -C3 -r1.8 -r1.9
*** index.html 1997/02/22 17:22:32 1.8
--- index.html 1997/04/25 00:06:59 1.9
***************
*** 26,31 ****
--- 26,32 ----
<ul>
<li><A HREF="install.html">Compiling and Installing Apache</A>
<li><A HREF="invoking.html">Starting Apache</A>
+ <li><A HREF="stopping.html">Stopping or Restarting Apache</A>
<li><A HREF="mod/directives.html">Apache run-time configuration directives</A>
<li><A HREF="mod/">Apache modules</A>
<li><A HREF="handler.html">Apache's handler use</A>
1.9 +3 -2 apache/htdocs/manual/invoking.html
Index: invoking.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/invoking.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -C3 -r1.8 -r1.9
*** invoking.html 1997/02/03 02:01:09 1.8
--- invoking.html 1997/04/25 00:06:59 1.9
***************
*** 92,99 ****
the file <code>logs/httpd.pid</code>. This filename can be changed with the
<A HREF="mod/core.html#pidfile">PidFile</A> directive. The process-id is for
use by the administrator in restarting and terminating the daemon;
! A HUP signal causes the daemon to re-read its configuration files and
! a TERM signal causes it to die gracefully.
<p>
If the process dies (or is killed) abnormally, then it will be necessary to
kill the children httpd processes.
--- 92,100 ----
the file <code>logs/httpd.pid</code>. This filename can be changed with the
<A HREF="mod/core.html#pidfile">PidFile</A> directive. The process-id is for
use by the administrator in restarting and terminating the daemon;
! A HUP or USR1 signal causes the daemon to re-read its configuration files and
! a TERM signal causes it to die gracefully. For more information
! see the <a href="stopping.html">Stopping and Restarting</a> page.
<p>
If the process dies (or is killed) abnormally, then it will be necessary to
kill the children httpd processes.
1.3 +7 -6 apache/htdocs/manual/stopping.html
Index: stopping.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/stopping.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -C3 -r1.2 -r1.3
*** stopping.html 1997/04/24 21:08:11 1.2
--- stopping.html 1997/04/25 00:06:59 1.3
***************
*** 57,62 ****
--- 57,67 ----
<p><b>Note:</b> prior to release 1.2b9 this code is quite unstable and
shouldn't be used at all.
+ <p><b>Note:</b> 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 a file.
+
<p>The <code>USR1</code> signal causes the parent process to <i>advise</i>
the children to exit after their current request (or to exit immediately
if they're not serving anything). The parent re-reads its configuration
***************
*** 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>,
--- 69,74 ----
***************
*** 114,120 ****
<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.
--- 114,121 ----
<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 (by the
! parent or children). 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.
1.18 +1 -1 apache/htdocs/manual/mod/mod_proxy.html
Index: mod_proxy.html
===================================================================
RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_proxy.html,v
retrieving revision 1.17
retrieving revision 1.18
diff -C3 -r1.17 -r1.18
*** mod_proxy.html 1997/04/21 03:12:06 1.17
--- mod_proxy.html 1997/04/25 00:07:02 1.18
***************
*** 199,205 ****
<strong>Context:</strong> server config<br>
<strong>Status:</strong> Base<br>
<strong>Module:</strong> mod_proxy<br>
! <strong>Compatibility:</strong> CacheLastModified is only available in
Apache 1.1 and later.<p>
If the origin HTTP server did not supply an expiry date for the
--- 199,205 ----
<strong>Context:</strong> server config<br>
<strong>Status:</strong> Base<br>
<strong>Module:</strong> mod_proxy<br>
! <strong>Compatibility:</strong> CacheLastModifiedFactor is only available in
Apache 1.1 and later.<p>
If the origin HTTP server did not supply an expiry date for the