For quite some time now, 'graceful' and 'restart' have done a config

file syntax check prior to actually attempting to restart. These notes
are no longer true.


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

1 files changed, 14 insertions, 14 deletions

diff --git a/docs/manual/stopping.xml b/docs/manual/stopping.xml
index e99ab45d7d..71822fd487 100644
--- a/docs/manual/stopping.xml
+++ b/docs/manual/stopping.xml
@@ -142,16 +142,15 @@
     low bandwidth links then you could wait 15 minutes before doing
     anything with the old log.</p>
 
-    <note>If your configuration file has errors
-    in it when you issue a restart then your parent will not
-    restart, it will exit with an error. 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. Before doing a restart, you can check the
-    syntax of the configuration files with the <code>-t</code>
-    command line argument (see <program>httpd</program>). This still will not
+    <note>
+    <p>When you issue a restart, a syntax check is first run, to
+    ensure that there are no errors in the configuration files.
+    If your configuration file has errors in it, you will get an
+    error message about that syntax error, and the server will refuse to
+    restart. This avoids the situation where the server halts and then 
+    cannot restart, leaving you with a non-functioning server.</p>
+
+    <p>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 <program>httpd</program> as a non-root user. If there
@@ -159,7 +158,7 @@
     because it's not root (or because the currently running
     <program>httpd</program> 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.</note>
+    should be fixed before issuing the graceful restart.</p></note>
 </section>
 
 <section id="hup"><title>Restart Now</title>
@@ -178,9 +177,10 @@
     will notice that the server statistics are set to zero when a
     <code>HUP</code> is sent.</p>
 
-<note>If your configuration file has errors in it when you issue a
-restart then your parent will not restart, it will exit with an
-error. See above for a method of avoiding this.</note>
+<note>As with a graceful restart, a syntax check is run before the the
+restart is attempted. If your configuration file has errors in it, the
+restart will not be attempted, and you will receive notification of the
+syntax error(s).</note>
 </section>
 
 <section id="gracefulstop"><title>Graceful Stop</title>