From: pcs <pcs@unknown>
Date: Sat, 22 May 1999 13:12:39 +0000 (+0000)
Subject: Note that -t may is useful to test configurations before doing a restart
X-Git-Tag: apache-apr-merge-3~4
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=40033fde0ff2d6793802482bb882c3da00307bfa;p=thirdparty%2Fapache%2Fhttpd.git

Note that -t may is useful to test configurations before doing a restart


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

diff --git a/docs/manual/stopping.html b/docs/manual/stopping.html
index fe5889cfe6e..783d1c02508 100644
--- a/docs/manual/stopping.html
+++ b/docs/manual/stopping.html
@@ -126,13 +126,18 @@ In the case of graceful
 restarts it will also leave children running when it exits.  (These are
 the children which are "gracefully exiting" by handling their last request.)
 This will cause problems if you attempt to restart the server -- it will
-not be able to bind to its listening ports.  At present the only work
-around is to check the syntax of your files before doing a restart.  The
-easiest way is to just run 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.
+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.
+
 
 <H3>Appendix: signals and race conditions</H3>
 
diff --git a/docs/manual/stopping.html.en b/docs/manual/stopping.html.en
index fe5889cfe6e..783d1c02508 100644
--- a/docs/manual/stopping.html.en
+++ b/docs/manual/stopping.html.en
@@ -126,13 +126,18 @@ In the case of graceful
 restarts it will also leave children running when it exits.  (These are
 the children which are "gracefully exiting" by handling their last request.)
 This will cause problems if you attempt to restart the server -- it will
-not be able to bind to its listening ports.  At present the only work
-around is to check the syntax of your files before doing a restart.  The
-easiest way is to just run 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.
+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.
+
 
 <H3>Appendix: signals and race conditions</H3>