From 4ae2b6fbf48e24a1a8fff4a31e7b8dd520f0a6e2 Mon Sep 17 00:00:00 2001 From: Rich Bowen Date: Sat, 10 Jun 2006 03:55:12 +0000 Subject: [PATCH] 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 --- docs/manual/stopping.html.en | 28 ++++++++++++++-------------- docs/manual/stopping.xml | 28 ++++++++++++++-------------- 2 files changed, 28 insertions(+), 28 deletions(-) diff --git a/docs/manual/stopping.html.en b/docs/manual/stopping.html.en index a518eb26cd..888726ca63 100644 --- a/docs/manual/stopping.html.en +++ b/docs/manual/stopping.html.en @@ -140,16 +140,15 @@ low bandwidth links then you could wait 15 minutes before doing anything with the old log.

-
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 -t - command line argument (see httpd). This still will not +
+

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.

+ +

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 @@ -157,7 +156,7 @@ 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.

+ should be fixed before issuing the graceful restart.

top

Restart Now

@@ -176,9 +175,10 @@ will notice that the server statistics are set to zero when a HUP is sent.

-
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.
+
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).
top

Graceful Stop

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.

- 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 -t - command line argument (see httpd). This still will not + +

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.

+ +

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 @@ -159,7 +158,7 @@ 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. + should be fixed before issuing the graceful restart.
Restart Now @@ -178,9 +177,10 @@ will notice that the server statistics are set to zero when a HUP is sent.

-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. +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).
Graceful Stop -- 2.40.0