You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by sl...@apache.org on 2001/02/27 22:45:03 UTC
cvs commit: httpd-2.0/docs/manual stopping.html
slive 01/02/27 13:45:03
Modified: docs/manual stopping.html
Log:
Move link on httpd command line documentation. Add link to
scoreboardfile directive documentation.
Submitted by: Herve Dumont <hd...@club-internet.fr>
Revision Changes Path
1.20 +11 -10 httpd-2.0/docs/manual/stopping.html
Index: stopping.html
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/stopping.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -d -b -u -r1.19 -r1.20
--- stopping.html 2001/01/28 00:19:30 1.19
+++ stopping.html 2001/02/27 21:45:02 1.20
@@ -115,15 +115,15 @@
cause problems if you attempt to restart the server -- it will not be
able to bind to its listening ports. Before doing a restart, you can
check the syntax of the configuration files with the <CODE>-t</CODE>
-command line argument (see <A HREF="invoking.html">Starting
-Apache</A>). This still will not guarantee that the server will
-restart correctly. To check the semantics of the configuration files
-as well as the syntax, you can try starting httpd as a non-root user.
-If there are no errors it will attempt to open its sockets and logs
-and fail because it's not root (or because the currently running httpd
-already has those ports bound). If it fails for any other reason then
-it's probably a config file error and the error should be fixed before
-issuing the graceful restart.
+command line argument (see <A
+HREF="programs/httpd.html">httpd</A>). This still will not guarantee
+that the server will restart correctly. To check the semantics of the
+configuration files as well as the syntax, you can try starting httpd
+as a non-root user. If there are no errors it will attempt to open
+its sockets and logs and fail because it's not root (or because the
+currently running httpd already has those ports bound). If it fails
+for any other reason then it's probably a config file error and the
+error should be fixed before issuing the graceful restart.
<H3>Restart Now</H3>
@@ -167,7 +167,8 @@
slot. So it might be advisable to use graceful restarts, with
an occasional hard restart. These problems are very difficult to work
around, but fortunately most architectures do not require a scoreboard file.
-See the ScoreBoardFile documentation for a method to determine if your
+See the <a HREF=
+"mod/core.html#scoreboardfile">ScoreBoardFile</a> documentation for a
architecture uses it.
<P><CODE>NEXT</CODE> and <CODE>MACHTEN</CODE> (68k only) have small race