Add a new command-line option -T that's the same as -t, but it does

not do DirectoryRoot checking. This assumes:

   1. command-line options are prefered over Config directives
   2. we want to maintain current behavior while making
      life easier for mass vhosting
   3. everybody's happy

I leave the decision to whether apachectl should use -t or -T
to others.

PR:
Obtained from:
Submitted by:
Reviewed by:


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

1 files changed, 11 insertions, 1 deletions

diff --git a/docs/manual/invoking.html.en b/docs/manual/invoking.html.en
index 6b0be6decb..02ee07659f 100644
--- a/docs/manual/invoking.html.en
+++ b/docs/manual/invoking.html.en
@@ -117,7 +117,17 @@ server. (Up to Apache 1.3.3, this option also started the server).
 <DD>Test the configuration file syntax (<EM>i.e.</EM>, read all configuration files
 and interpret them) but do not start the server. If the configuration contains
 errors, display an error message and exit with a non-zero exit status,
-otherwise display "Syntax OK" and terminate with a zero exit status.
+otherwise display "Syntax OK" and terminate with a zero exit status. This
+command checks to see if all DocumentRoot entries exist and are directories.
+For sites with many vhosts, this is expensive; consider the <CODE>-T</CODE>
+command instead.
+
+<DT><CODE>-T</CODE>
+<DD>Test the configuration file syntax (<EM>i.e.</EM>, read all configuration files
+and interpret them) but do not start the server. If the configuration contains
+errors, display an error message and exit with a non-zero exit status,
+otherwise display "Syntax OK" and terminate with a zero exit status. This
+command does not perform any checking of the DocumentRoot entries.
 
 <DT><CODE>-k</CODE> <EM>option</EM>
 <DD>Windows only: signal Apache to restart or shutdown. <EM>option</EM>