cvs commit: apache-1.3/htdocs/manual windows.html
stoddard99/07/22 10:51:02 Modified:htdocs/manual windows.html Log: Update windows documentation to address questions on the newsgroups and PR database. Revision ChangesPath 1.30 +14 -1 apache-1.3/htdocs/manual/windows.html Index: windows.html === RCS file: /home/cvs/apache-1.3/htdocs/manual/windows.html,v retrieving revision 1.29 retrieving revision 1.30 diff -u -r1.29 -r1.30 --- windows.html 1999/04/20 19:18:41 1.29 +++ windows.html 1999/07/22 17:50:59 1.30 @@ -68,6 +68,14 @@ but may not be necessary. If running on NT 4.0, installing Service Pack 2 is recommended. +P + +STRONGNote: Winsock 2 is required for Apache 1.3.7 and later./STRONG + +P + +Winsock 2 for Windows 95 is available A HREF=http://www.microsoft.com/windows95/downloads/;here./A + H2A NAME=downDownloading Apache for Windows/A/H2 PInformation on the latest version of Apache can be found on the @@ -274,6 +282,11 @@ /UL H2A NAME=serviceRunning Apache for Windows as a Service/A/H2 + STRONGNote: The -n option to specify a service name is only available + with Apache 1.3.7 and later. Earlier versions of Apache only support + the default service name 'Apache'./STRONG + +P You can install Apache as a Windows NT service as follows: @@ -328,7 +341,7 @@ PREapache -f c:\my server\conf\my.conf/PRE PREapache -f test\test.conf/PRE UL -LI-n specifies the configuration file of an installed Apache service +LI-n specifies the configuration file of an installed Apache service (Apache 1.3.7 and later) /UL PREapache -n service name/PRE
cvs commit: apache-1.3/htdocs/manual windows.html
dgaudet 99/04/20 12:18:42 Modified:htdocs/manual windows.html Log: note about 127.0.0.1 PR: 4155 Revision ChangesPath 1.29 +6 -0 apache-1.3/htdocs/manual/windows.html Index: windows.html === RCS file: /home/cvs/apache-1.3/htdocs/manual/windows.html,v retrieving revision 1.28 retrieving revision 1.29 diff -u -r1.28 -r1.29 --- windows.html 1999/04/08 21:56:40 1.28 +++ windows.html 1999/04/20 19:18:41 1.29 @@ -202,6 +202,12 @@ This should respond with a welcome page, and a link to the Apache manual. If nothing happens or you get an error, look in the SAMPerror_log/SAMP file in the SAMPlogs/SAMP directory. +If your host isn't connected to the net, you may have to use +this URL: + +PRE + http://127.0.0.1/ +/PRE P
cvs commit: apache-1.3/htdocs/manual windows.html
stoddard99/04/08 14:56:43 Modified:htdocs/manual windows.html Log: Some documentation on the multiple services patch Submitted by: Keith Wannamaker Revision ChangesPath 1.28 +95 -30apache-1.3/htdocs/manual/windows.html Index: windows.html === RCS file: /export/home/cvs/apache-1.3/htdocs/manual/windows.html,v retrieving revision 1.27 retrieving revision 1.28 diff -u -r1.27 -r1.28 --- windows.html 1999/03/19 16:07:18 1.27 +++ windows.html 1999/04/08 21:56:40 1.28 @@ -47,7 +47,9 @@ LIA HREF=#runRunning Apache for Windows/A LIA HREF=#useUsing Apache for Windows/A LIA HREF=#cmdlineRunning Apache for Windows from the Command Line/A - LIA HREF=#signalSignalling Apache when running/A + LIA HREF=#serviceRunning Apache for Windows as a Service/A + LIA HREF=#signalSignalling Console Apache when running/A + LIA HREF=#signalsrvSignalling Service Apache when running/A LIA HREF=#compCompiling Apache for Windows/A /UL @@ -145,7 +147,7 @@ There are two ways you can run Apache: UL - LIAs a service (available on NT only). This is the best option if + LIAs a A HREF=#serviceservice/A (available on NT only). This is the best option if you want Apache to automatically start when you machine boots, and to keep Apache running when you log-off. @@ -155,12 +157,14 @@ /UL To start Apache as a service, you first need to install it as a -service. Run the Install Apache as Service (NT only) option from the -Start menu. Once this is done you can start Apache by opening the -Services window (in the Control Panel), selecting Apache, then -clicking on Start. Apache will now be running in the background. You +service. Multiple Apache services can be installed, each with a +different name and configuration. To install the default Apache +service named Apache, run the Install Apache as Service (NT only) +option from the Start menu. Once this is done you can start the Apache +service by opening the Services window (in the Control Panel), selecting Apache, +then clicking on Start. Apache will now be running in the background. You can later stop Apache by clicking on Stop. As an alternative to using -the Services window, you can start and stop Apache from the control +the Services window, you can start and stop the Apache service from the control line with PRE @@ -168,6 +172,11 @@ NET STOP APACHE /PRE +See A HREF=#signalsrvSignalling Service Apache when Running/A +for more information on installing and controlling Apache services. + +P + To run Apache from a console window, select the Start Apache as console app option from the Start menu (in Apache 1.3.4 and earlier, this option was called Apache Server). This will open a console @@ -175,7 +184,7 @@ active until you stop Apache. To stop Apache running, either select the Shutdown Apache console app icon option from the Start menu (this is not available in Apache 1.3.4 or earlier), or see A -HREF=#signalSignalling Apache when Running/A for how +HREF=#signalSignalling Console Apache when Running/A for how to control Apache from the command line. P @@ -258,6 +267,44 @@ is available./A /UL +H2A NAME=serviceRunning Apache for Windows as a Service/A/H2 + +You can install Apache as a Windows NT service as follows: + +PRE +apache -i -n service name +/PRE + +To install a service to use a particular configuration, specify the +configuration file when the service is installed: + +PRE +apache -i -n service name -f \my server\conf\my.conf +/PRE + +To remove an Apache service, use + +PRE +apache -u -n service name +/PRE + +The default service name, if one is not specified, is Apache. + +P + +Once a service is installed, you can use the SAMP-n/SAMP option, in conjunction +with other options, to refer to a service's configuration file. For example:br + +To test a service's configuration file: +PRE +apache -n service name -t +/PRE + +To start a console Apache using a service's configuration file: +PRE +apache -n service name +/PRE + H2A NAME=cmdlineRunning Apache for Windows from the Command Line/A/H2 The Start menu icons and the NT Service manager can provide a simple @@ -266,29 +313,44 @@ P When working with Apache it is important to know how it will find the -configuration files. Apache will try one of the following, in this order. +configuration files. You can specify a configuration file on the command line +in two ways: UL +LI-f specifies a path to a particular configuration file +/UL +PREapache -f c:\my server\conf\my.conf/PRE +PREapache -f test\test.conf/PRE +UL +LI-n specifies the configuration file of an
cvs commit: apache-1.3/htdocs/manual windows.html
pcs 99/03/19 08:02:20 Modified:htdocs/manual windows.html Log: Note that Apache may run on Windows 98 (since at least some bug reports say they've tried it). Describe the new Apache Start menu options for starting and stopping the Apache console application. Revision ChangesPath 1.26 +10 -8 apache-1.3/htdocs/manual/windows.html Index: windows.html === RCS file: /export/home/cvs/apache-1.3/htdocs/manual/windows.html,v retrieving revision 1.25 retrieving revision 1.26 diff -u -r1.25 -r1.26 --- windows.html 1999/01/10 05:47:07 1.25 +++ windows.html 1999/03/19 16:02:19 1.26 @@ -56,9 +56,9 @@ H2A NAME=reqRequirements/A/H2 Apache 1.3 is designed to run on Windows NT 4.0. The binary installer -will only work in Intel processors. Apache may also run on Windows 95 -and Windows NT 3.5.1, but these have not been tested. In all cases -TCP/IP networking must be installed. +will only work in Intel processors. Apache may also run on Windows 95, +Windows 98 and Windows NT 3.5.1, but these have not been tested. In +all cases TCP/IP networking must be installed. P @@ -168,11 +168,13 @@ NET STOP APACHE /PRE -To run Apache from a console window, select the Apache Server option -from the Start menu. This will open a console window and start Apache -running inside it. The window will remain active until you stop -Apache. To stop Apache running, see A HREF=#signalSAMPSignalling Apache -when Running/SAMP/A. +To run Apache from a console window, select the Start Apache as +console app option from the Start menu. This will open a console +window and start Apache running inside it. The window will remain +active until you stop Apache. To stop Apache running, either select +the Shutdown Apache console app icon option from the Start menu, or +see A HREF=#signalSAMPSignalling Apache when Running/SAMP/A +for how to control Apache from the command line. P
cvs commit: apache-1.3/htdocs/manual windows.html
pcs 99/03/19 08:07:18 Modified:htdocs/manual windows.html Log: Note the different Start menu option names between 1.3.4 and 1.3.5. Revision ChangesPath 1.27 +13 -11apache-1.3/htdocs/manual/windows.html Index: windows.html === RCS file: /export/home/cvs/apache-1.3/htdocs/manual/windows.html,v retrieving revision 1.26 retrieving revision 1.27 diff -u -r1.26 -r1.27 --- windows.html 1999/03/19 16:02:19 1.26 +++ windows.html 1999/03/19 16:07:18 1.27 @@ -155,13 +155,13 @@ /UL To start Apache as a service, you first need to install it as a -service. Run the Install Apache as Service option from the Start -menu. Once this is done you can start Apache by opening the Services -window (in the Control Panel), selecting Apache, then clicking on -Start. Apache will now be running in the background. You can later -stop Apache by clicking on Stop. As an alternative to using the -Services window, you can start and stop Apache from the control line -with +service. Run the Install Apache as Service (NT only) option from the +Start menu. Once this is done you can start Apache by opening the +Services window (in the Control Panel), selecting Apache, then +clicking on Start. Apache will now be running in the background. You +can later stop Apache by clicking on Stop. As an alternative to using +the Services window, you can start and stop Apache from the control +line with PRE NET START APACHE @@ -169,12 +169,14 @@ /PRE To run Apache from a console window, select the Start Apache as -console app option from the Start menu. This will open a console +console app option from the Start menu (in Apache 1.3.4 and earlier, +this option was called Apache Server). This will open a console window and start Apache running inside it. The window will remain active until you stop Apache. To stop Apache running, either select -the Shutdown Apache console app icon option from the Start menu, or -see A HREF=#signalSAMPSignalling Apache when Running/SAMP/A -for how to control Apache from the command line. +the Shutdown Apache console app icon option from the Start menu +(this is not available in Apache 1.3.4 or earlier), or see A +HREF=#signalSignalling Apache when Running/A for how +to control Apache from the command line. P
cvs commit: apache-1.3/htdocs/manual windows.html
fielding99/01/09 21:47:08 Modified:htdocs/manual windows.html Log: Fix typos, update for new makefiles. Revision ChangesPath 1.25 +26 -26apache-1.3/htdocs/manual/windows.html Index: windows.html === RCS file: /home/cvs/apache-1.3/htdocs/manual/windows.html,v retrieving revision 1.24 retrieving revision 1.25 diff -u -r1.24 -r1.25 --- windows.html 1998/10/22 20:48:40 1.24 +++ windows.html 1999/01/10 05:47:07 1.25 @@ -17,7 +17,7 @@ H1 ALIGN=CENTERUsing Apache With Microsoft Windows/H1 PThis document explains how to install, configure and run - Apache 1.3b6 and later under Microsoft Windows. Please note that at + Apache 1.3 under Microsoft Windows. Please note that at this time, Windows support is entirely experimental, and is recommended only for experienced users. The Apache Group does not guarantee that this software will work as documented, or even at @@ -132,19 +132,6 @@ P -BLOCKQUOTE -STRONGImportant note for 1.3b6 installs/STRONG: the above only -applies for 1.3b7 and later. In 1.3b6 the installer would overwrite -any existing SAMPhttpd.conf/SAMP, SAMPaccess.conf/SAMP, -SAMPsrm.conf/SAMP or SAMPmime.types/SAMP files in the -SAMPconf/SAMP, and will also overwrite your -SAMPindex.html/SAMP file in the SAMPhtdocs/SAMP directory. You -should copy these files or directories before installing Apache 1.3b6 -or install into a new directory. -/BLOCKQUOTE - -P - After installing Apache, you should edit the configuration files in the SAMPconf/SAMP directory as required. These files will be configured during the install ready for Apache to be run from the @@ -269,8 +256,8 @@ H2A NAME=cmdlineRunning Apache for Windows from the Command Line/A/H2 -The Start menu icons and the NT Service manager can provide an simple -interafce for administering Apache. But in some cases it is easier to +The Start menu icons and the NT Service manager can provide a simple +interface for administering Apache. But in some cases it is easier to work from the command line. P @@ -295,27 +282,27 @@ effect on Apache's behavior. P -Under windows, when invoked from the start menu or the Service Manager Apache is -usually passed no arguments. So using the registry entry is the perfered +When invoked from the start menu or the Service Manager, Apache is +usually passed no arguments, so using the registry entry is the preferred technique. P During a binary installation, a registry key will have been installed, for example: PRE - HKEY_LOCAL_MACHINE\Software\Apache Group\Apache\1.3.1\ServerRoot + HKEY_LOCAL_MACHINE\Software\Apache Group\Apache\1.3.4\ServerRoot /PRE P This key is compiled into the server and can enable you to test new versions without affecting the current version. Of course you must take care not to install the new version on top of the -old version in the file system. You can not run two invocations +old version in the file system. You cannot run two invocations of Apache on Windows simultaneously. P If you did not do a binary install then Apache will in some -senarios complain that about the missing registry key. This +scenarios complain that about the missing registry key. This warning can be ignored if it otherwise was able to find it's configuration files. @@ -344,7 +331,7 @@ P -To install Apache as a Windows NT service as follows: +You can install Apache as a Windows NT service as follows: PRE apache -i @@ -359,7 +346,7 @@ H2A NAME=signalSignalling Apache when running/A/H2 -On Windows 95 Apache runs as a console application. You can tell a +On Windows 95, Apache runs as a console application. You can tell a running Apache to stop by opening another console window and running PRE @@ -410,13 +397,19 @@ CODEsrc/CODE subdirectory of the Apache distribution./P PThe master Apache makefile instructions are contained in the - CODEMakefile.nt/CODE file. To compile Apache, simply use one of - the following commands: + CODEMakefile.nt/CODE file. To compile Apache on Windows NT, simply + use one of the following commands: UL LICODEnmake /f Makefile.nt _apacher/CODE (release build) LICODEnmake /f Makefile.nt _apached/CODE (debug build) /UL +Pem(1.3.4 and later)/em To compile Apache on Windows 95, use one of +UL +LICODEnmake /f Makefile_win32.txt/CODE (release build) +LICODEnmake /f Makefile_win32_debug.txt/CODE (debug build) +/UL + PThese will both compile Apache. The latter will include debugging information in the resulting files, making it easier to find bugs and track down problems./P @@ -454,8 +447,15 @@ LICODEnmake /f Makefile.nt installd
cvs commit: apache-1.3/htdocs/manual windows.html
coar98/10/22 13:48:41 Modified:htdocs/manual windows.html Log: Fix some broken HTML, and note that the -k option stuff is new with 1.3.3. PR: 3252 Revision ChangesPath 1.24 +15 -3 apache-1.3/htdocs/manual/windows.html Index: windows.html === RCS file: /export/home/cvs/apache-1.3/htdocs/manual/windows.html,v retrieving revision 1.23 retrieving revision 1.24 diff -u -r1.23 -r1.24 --- windows.html 1998/10/07 08:52:31 1.23 +++ windows.html 1998/10/22 20:48:40 1.24 @@ -184,8 +184,8 @@ To run Apache from a console window, select the Apache Server option from the Start menu. This will open a console window and start Apache running inside it. The window will remain active until you stop -Apache. To stop Apache running, see A HREF=#signalSignalling Apache -when Running/SAMP. +Apache. To stop Apache running, see A HREF=#signalSAMPSignalling Apache +when Running/SAMP/A. P @@ -365,7 +365,13 @@ PRE apache -k shutdown /PRE +BLOCKQUOTE + STRONGNote: This option is only available with Apache 1.3.3 and + later. For earlier versions, you need to use Control-C in the + Apache console window to shut down the server./STRONG +/BLOCKQUOTE +P This should be used instead of pressing Control-C in the running Apache console window, because it lets Apache end any current transactions and cleanup gracefully. @@ -379,10 +385,16 @@ PRE apache -k restart /PRE +BLOCKQUOTE + STRONGNote: This option is only available with Apache 1.3.3 and + later. For earlier versions, you need to use Control-C in the + Apache console window to shut down the server./STRONG +/BLOCKQUOTE +P Note for people familiar with the Unix version of Apache: these commands provide a Windows equivalent to CODEkill -TERM -ipid/i/CODE and CODEkill -USR1 ipid/i/CODE. The command +EMpid/EM/CODE and CODEkill -USR1 EMpid/EM/CODE. The command line option used, CODE-k/CODE, was chosen as a reminder of the kill command used on Unix.
cvs commit: apache-1.3/htdocs/manual windows.html
pcs 98/10/07 01:52:32 Modified:htdocs/manual windows.html Log: Document the -k command line argument. This is based on a previous patch to add this documentation from [EMAIL PROTECTED] (16 Jun 1998). Revision ChangesPath 1.23 +33 -3 apache-1.3/htdocs/manual/windows.html Index: windows.html === RCS file: /export/home/cvs/apache-1.3/htdocs/manual/windows.html,v retrieving revision 1.22 retrieving revision 1.23 diff -u -r1.22 -r1.23 --- windows.html 1998/09/17 14:14:49 1.22 +++ windows.html 1998/10/07 08:52:31 1.23 @@ -17,7 +17,7 @@ H1 ALIGN=CENTERUsing Apache With Microsoft Windows/H1 PThis document explains how to install, configure and run - Apache 1.3 under Microsoft Windows. Please note that at + Apache 1.3b6 and later under Microsoft Windows. Please note that at this time, Windows support is entirely experimental, and is recommended only for experienced users. The Apache Group does not guarantee that this software will work as documented, or even at @@ -47,6 +47,7 @@ LIA HREF=#runRunning Apache for Windows/A LIA HREF=#useUsing Apache for Windows/A LIA HREF=#cmdlineRunning Apache for Windows from the Command Line/A + LIA HREF=#signalSignalling Apache when running/A LIA HREF=#compCompiling Apache for Windows/A /UL @@ -183,8 +184,8 @@ To run Apache from a console window, select the Apache Server option from the Start menu. This will open a console window and start Apache running inside it. The window will remain active until you stop -Apache. To stop Apache running, press Control-C within the console -window. +Apache. To stop Apache running, see A HREF=#signalSignalling Apache +when Running/SAMP. P @@ -355,6 +356,35 @@ apache -u /PRE + +H2A NAME=signalSignalling Apache when running/A/H2 + +On Windows 95 Apache runs as a console application. You can tell a +running Apache to stop by opening another console window and running + +PRE +apache -k shutdown +/PRE + +This should be used instead of pressing Control-C in the running +Apache console window, because it lets Apache end any current +transactions and cleanup gracefully. + +P + +You can also tell Apache to restart. This makes it re-read the +configuration files. Any transactions in progress are allowed to +complete without interruption. To restart Apache, run + +PRE +apache -k restart +/PRE + +Note for people familiar with the Unix version of Apache: these +commands provide a Windows equivalent to CODEkill -TERM +ipid/i/CODE and CODEkill -USR1 ipid/i/CODE. The command +line option used, CODE-k/CODE, was chosen as a reminder of the +kill command used on Unix. H2A NAME=compCompiling Apache for Windows/A/H2
cvs commit: apache-1.3/htdocs/manual windows.html
brian 98/07/22 13:23:35 Modified:htdocs/manual windows.html Log: Remove reference to 1.3b6 which may have confused people, and remove documentation for not-completely-implemented feature. Revision ChangesPath 1.19 +1 -29 apache-1.3/htdocs/manual/windows.html Index: windows.html === RCS file: /export/home/cvs/apache-1.3/htdocs/manual/windows.html,v retrieving revision 1.18 retrieving revision 1.19 diff -u -r1.18 -r1.19 --- windows.html 1998/07/21 09:33:29 1.18 +++ windows.html 1998/07/22 20:23:33 1.19 @@ -17,7 +17,7 @@ H1 ALIGN=CENTERUsing Apache With Microsoft Windows/H1 PThis document explains how to install, configure and run - Apache 1.3b6 and later under Microsoft Windows. Please note that at + Apache 1.3 under Microsoft Windows. Please note that at this time, Windows support is entirely experimental, and is recommended only for experienced users. The Apache Group does not guarantee that this software will work as documented, or even at @@ -360,34 +360,6 @@ apache -u /PRE - -H2A NAME=signalSignalling Apache when running/A/H2 - -PWhen Apache is running you may request that it reread it's -configuration files as follows: - -PRE -apache -Z @@whatever?@@ -/PRE - -and to request that it shutdown gracefully, via: - -PRE -apache -Z @@whatever?@@ -/PRE - -and you can force it to stop via: - -PRE -apache -Z @@whatever?@@ -/PRE - - -P -Other techinques of shutting down the server (e.g. using the -task manager to End Process, distroying the command -window containing the server, or using control-C to interupt -it) all have the downside of @@whatever@@. H2A NAME=compCompiling Apache for Windows/A/H2
cvs commit: apache-1.3/htdocs/manual windows.html
brian 98/07/22 13:25:41 Modified:htdocs/manual windows.html Log: Followup to previous commit - another reference to beta remove, the link to previously removed text also removed, and 1.3.0 -- 1.3.1. Revision ChangesPath 1.20 +1 -7 apache-1.3/htdocs/manual/windows.html Index: windows.html === RCS file: /export/home/cvs/apache-1.3/htdocs/manual/windows.html,v retrieving revision 1.19 retrieving revision 1.20 diff -u -r1.19 -r1.20 --- windows.html 1998/07/22 20:23:33 1.19 +++ windows.html 1998/07/22 20:25:40 1.20 @@ -47,7 +47,6 @@ LIA HREF=#runRunning Apache for Windows/A LIA HREF=#useUsing Apache for Windows/A LIA HREF=#cmdlineRunning Apache for Windows from the Command Line/A - LIA HREF=#signalSignalling Apache when running/A LIA HREF=#compCompiling Apache for Windows/A /UL @@ -302,12 +301,7 @@ During a binary installation, a registry key will have been installed, for example: PRE - HKEY_LOCAL_MACHINE\Software\Apache Group\Apache\1.3.0\ServerRoot -/PRE - -For the 1.3 beta releases the key was: -PRE - HKEY_LOCAL_MACHINE\Software\Apache Group\Apache\1.3 beta\ServerRoot + HKEY_LOCAL_MACHINE\Software\Apache Group\Apache\1.3.1\ServerRoot /PRE P
cvs commit: apache-1.3/htdocs/manual windows.html
pcs 98/07/21 02:33:29 Modified:htdocs/manual windows.html Log: Be more explicit when explaining how to compile from DSP files. Add references to the projects to build uri_delims and test_chars files. Give a suggested compilation order. Revision ChangesPath 1.18 +18 -10apache-1.3/htdocs/manual/windows.html Index: windows.html === RCS file: /export/home/cvs/apache-1.3/htdocs/manual/windows.html,v retrieving revision 1.17 retrieving revision 1.18 diff -u -r1.17 -r1.18 --- windows.html 1998/06/16 02:40:32 1.17 +++ windows.html 1998/07/21 09:33:29 1.18 @@ -413,17 +413,25 @@ track down problems./P PApache can also be compiled using VC++'s Visual Studio development - environment. Although compiling Apache in this manner is not as simple, - it makes it possible to easily modify the Apache source, or to compile - Apache if the command-line tools are not installed./P + environment. Although compiling Apache in this manner is not as + simple, it makes it possible to easily modify the Apache source, or + to compile Apache if the command-line tools are not installed. + Project files (CODE.DSP/CODE) are included for each of the + portions of Apache. To build Apache from the these projects files + you will need to build the following projects iin this order/i: -PProject files (CODE.DSP/CODE) are included for each of the - portions of Apache. The three projects that are necessary for - Apache to run are CODEApache.dsp/CODE, CODEap/ap.dsp/CODE, - CODEregex/regex.dsp/CODE, CODEApacheCore.dsp/CODE and - CODEos/win32/ApacheOS.dsp/CODE. The CODEsrc/win32/CODE - subdirectory contains project files for the optional modules (see - below)./P + OL + LICODEos\win32\ApacheOS.dsp/CODE + LICODEregex\regex.dsp/CODE + LICODEap\ap.dsp/CODE + LICODEmain\gen_uri_delims.dsp/CODE + LICODEmain\gen_test_char.dsp/CODE + LICODEApacheCore.dsp/CODE + LICODEApache.dsp/CODE + /OL + + In addition, the CODEsrc\os\win32/CODE subdirectory contains + project files for the optional modules (see below)./P POnce Apache has been compiled, it needs to be installed in its server root directory. The default is the CODE\Apache/CODE
cvs commit: apache-1.3/htdocs/manual windows.html
brian 98/06/15 19:40:33 Modified:htdocs/manual windows.html Log: Submitted by: [EMAIL PROTECTED] Reviewed by: Brian More good details added, more work needed... Revision ChangesPath 1.17 +82 -32apache-1.3/htdocs/manual/windows.html Index: windows.html === RCS file: /export/home/cvs/apache-1.3/htdocs/manual/windows.html,v retrieving revision 1.16 retrieving revision 1.17 diff -u -r1.16 -r1.17 --- windows.html 1998/05/30 12:18:01 1.16 +++ windows.html 1998/06/16 02:40:32 1.17 @@ -47,6 +47,7 @@ LIA HREF=#runRunning Apache for Windows/A LIA HREF=#useUsing Apache for Windows/A LIA HREF=#cmdlineRunning Apache for Windows from the Command Line/A + LIA HREF=#signalSignalling Apache when running/A LIA HREF=#compCompiling Apache for Windows/A /UL @@ -152,7 +153,7 @@ which should be set before you start really using Apache. However to get started quickly the files should work as installed. -H2A NAME=instRunning Apache for Windows/A/H2 +H2A NAME=runRunning Apache for Windows/A/H2 There are two ways you can run Apache: @@ -161,7 +162,7 @@ you want Apache to automatically start when you machine boots, and to keep Apache running when you log-off. - LIFrom a console window. This is the only option available for + LIFrom a a ref=#cmdlineconsole window/a. This is the only option available for Windows 95 users. /UL @@ -272,32 +273,57 @@ work from the command line. P - When working with Apache it is important to know how it will find the -configuration files. During installation, a registry key will have -been installed. For the 1.3 beta releases the key is: +configuration files. Apache will try one of the following, in this order. -PRE - HKEY_LOCAL_MACHINE\Software\Apache Group\Apache\1.3 beta\ServerRoot -/PRE +ul +liA ServerRoot directive via a -C switch. +liThe -f switch on the command line. +liThe -d switch on the command line. +liA registry entry, created if you did a binary install. +liThe server root compiled into the server. +/ul -While for the final 1.3.0 release it is called: +P +The server root compiled into the server is usually /apache. +invoking apache with the -v switch will display this value +labeled as HTTPD_ROOT. + +P +Your current working directory when Apache is started up has no +effect on Apache's behavior. + +P +Under windows, when invoked from the start menu or the Service Manager Apache is +usually passed no arguments. So using the registry entry is the perfered +technique. +P +During a binary installation, a registry key will have +been installed, for example: PRE HKEY_LOCAL_MACHINE\Software\Apache Group\Apache\1.3.0\ServerRoot /PRE -(The use of different keys lets you install later versions without -affect any previous versions already installed. For example, when -1.3.1 comes out it will use 1.3.1 instead of 1.3.0 in the registry -key, so you can install and test 1.3.1 without affecting you existing -1.3.0 installation. Note however that Windows NT service manager only -ever allows one service with the same name, so you cannot install the -newer version as a service whilst the older version is still -installed). +For the 1.3 beta releases the key was: +PRE + HKEY_LOCAL_MACHINE\Software\Apache Group\Apache\1.3 beta\ServerRoot +/PRE P +This key is compiled into the server and can enable you to test +new versions without affecting the current version. Of course +you must take care not to install the new version on top of the +old version in the file system. You can not run two invocations +of Apache on Windows simultaneously. +P +If you did not do a binary install then Apache will in some +senarios complain that about the missing registry key. This +warning can be ignored if it otherwise was able to find it's +configuration files. + +P The value of this key is the ServerRoot directory, containing the SAMPconf/SAMP directory. When Apache starts it will read the SAMPhttpd.conf/SAMP file from this directory. If this file @@ -309,7 +335,6 @@ directory in the SAMPhttpd.conf/SAMP file to the new location. P - To run Apache from the command line as a console application, use the following command: @@ -317,14 +342,13 @@ apache -s /PRE -(The -s option is not required by Windows 95, but on Windows NT it -prevents Apache waiting to see if Apache is running as a -service). Apache will execute, and will remain running until it -is stopped by pressing control-C. +Apache will execute, and will remain running until it is stopped by pressing +control-C. (The -s option is not required by Windows 95, but on Windows NT it +prevents Apache waiting
cvs commit: apache-1.3/htdocs/manual windows.html
pcs 98/05/10 09:12:10 Modified:htdocs/manual windows.html Log: Update windows instructions for 1.3b6. Move compilation stuff to the end on the basis that most users will be interested in the pre-compiled installer. Document the registry key used and how it relates to command line arguments (-d, -f) and the ServerRoot directive. Show how to start and stop the Apache service from the command line. Revision ChangesPath 1.14 +230 -93 apache-1.3/htdocs/manual/windows.html Index: windows.html === RCS file: /export/home/cvs/apache-1.3/htdocs/manual/windows.html,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- windows.html 1998/03/30 02:40:15 1.13 +++ windows.html 1998/05/10 16:12:09 1.14 @@ -16,8 +16,8 @@ H1 ALIGN=CENTERUsing Apache With Microsoft Windows/H1 -PThis document explains how to compile, install, configure and run - Apache 1.3b3 (or later) under Microsoft Windows. Please note that at +PThis document explains how to install, configure and run + Apache 1.3b6 (or later) under Microsoft Windows. Please note that at this time, Windows support is entirely experimental, and is recommended only for experienced users. The Apache Group does not guarantee that this software will work as documented, or even at @@ -31,131 +31,165 @@ of webserver performance are asked to compare against Apache on a Unix platform such as Solaris, FreeBSD, or Linux./STRONG/P +P + +Most of this document assumes that you are installing Windows from a +binary distribution. If you want to compile Apache yourself (possibly +to help with development, or to track down bugs), see the section on +A HREF=#compCompiling Apache for Windows/A below. + HR UL LIA HREF=#reqRequirements/A LIA HREF=#downDownloading Apache for Windows/A - LIA HREF=#compCompiling Apache for Windows/A - LIA HREF=#instInstalling Apache for Windows/A + LIA HREF=#instInstalling Apache for Windows (binary install)/A + LIA HREF=#runRunning Apache for Windows/A LIA HREF=#useUsing Apache for Windows/A + LIA HREF=#cmdlineRunning Apache for Windows from the Command Line/A + LIA HREF=#compCompiling Apache for Windows/A /UL HR H2A name=reqRequirements/A/H2 -PApache 1.3b3 requires the following:/P +PApache 1.3b6 requires the following:/P UL LIMicrosoft Windows NT 4.0A HREF=#351*/A, or Windows 95. LIAn Intel-based PC-compatible capable of running above OS (exact requirements unknown) with a connection to a TCP/IP network. - LIMicrosoft Visual C++ 5.0 or later. /UL PSMALLA name=351*/A Apache may run with Windows NT 3.5.1, but has not been tested./SMALL/P -PThis documentation assumes good working knowledge of Microsoft - Windows, Microsoft Visual C++, and the Apache web server (for - Unix)./P - PIf running on Windows 95, using the Winsock2 upgrade is recommended but may not be necessary. If running on NT 4.0, installing Service Pack 2 is recommended./P H2A name=downDownloading Apache for Windows/A/H2 -PInformation on the latest version of Apache can be found on the Apache -web server at A +PInformation on the latest version of Apache can be found on the +Apache web server at A HREF=http://www.apache.org/;http://www.apache.org//A. This will list the current release, any more recent alpha or beta-test release, together with details of mirror web and anonymous ftp sites./P -PYou can download Apache 1.3b3 in two different forms: an InstallShield-based - CODE.exe/CODE file which contains the precompiled binary, and a - CODE.tar.gz/CODE which contains the source code (and is also the - regular Unix distribution). +P -H2A name=compCompiling Apache for Windows/A/H2 +You should download the version of Apache for Windows with the +CODE.exe/CODE extension. This is a single file containing Apache, +ready to install and run. There may also be a CODE.zip/CODE file +containing the source code, to compile Apache yourself. -PCompiling Apache requires Microsoft Visual C++ 5.0 to be properly - installed. It is easiest to compile with the command-line tools - (nmake, etc...). Consult the VC++ manual to determine how to install - them./P +H2A name=instInstalling Apache for Windows/A/H2 -PFirst, unpack the Apache distribution into an appropriate - directory. Open a command-line prompt, and change to the - CODEsrc/CODE subdirectory of the Apache distribution./P +Run the Apache SAMP.exe/SAMP file you downloaded above. This will +ask for: -PThe master Apache makefile instructions are contained in the - CODEMakefile.nt/CODE file. To compile Apache, simply use one of - the following commands: UL -LICODEnmake /f
cvs commit: apache-1.3/htdocs/manual windows.html
brian 98/03/29 18:40:16 Modified:htdocs/manual windows.html Log: Add some misc comments, probably unnecessary but always a good idea kind of thing. Revision ChangesPath 1.13 +4 -0 apache-1.3/htdocs/manual/windows.html Index: windows.html === RCS file: /export/home/cvs/apache-1.3/htdocs/manual/windows.html,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- windows.html 1998/03/21 17:00:54 1.12 +++ windows.html 1998/03/30 02:40:15 1.13 @@ -61,6 +61,10 @@ Windows, Microsoft Visual C++, and the Apache web server (for Unix)./P +PIf running on Windows 95, using the Winsock2 upgrade is recommended + but may not be necessary. If running on NT 4.0, installing Service Pack 2 + is recommended./P + H2A name=downDownloading Apache for Windows/A/H2 PInformation on the latest version of Apache can be found on the Apache
cvs commit: apache-1.3/htdocs/manual windows.html
pcs 98/03/21 09:00:56 Modified:htdocs/manual windows.html Log: Various updates: add libap to the list of required libraries. Remove reference to StartServers. Change links to mod_dll to mod_so. Revision ChangesPath 1.12 +14 -16apache-1.3/htdocs/manual/windows.html Index: windows.html === RCS file: /export/home/cvs/apache-1.3/htdocs/manual/windows.html,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- windows.html 1998/02/05 21:19:54 1.11 +++ windows.html 1998/03/21 17:00:54 1.12 @@ -104,12 +104,11 @@ PProject files (CODE.DSP/CODE) are included for each of the portions of Apache. The three projects that are necessary for - Apache to run are CODEApache.dsp/CODE, - CODEApacheCore.dsp/CODE and - CODEos/win32/ApacheOS.dsp/CODE. The regular expression library - in CODEregex/CODE also need to be compiled using the supplied - makefile. The CODEsrc/win32/CODE subdirectory contains project - files for the optional modules (see below)./P + Apache to run are CODEApache.dsp/CODE, CODEap/ap.dsp/CODE, + CODEregex/regex.dsp/CODE, CODEApacheCore.dsp/CODE and + CODEos/win32/ApacheOS.dsp/CODE. The CODEsrc/win32/CODE + subdirectory contains project files for the optional modules (see + below)./P H2A name=instInstalling Apache for Windows/A/H2 @@ -156,13 +155,12 @@ UL LIPBecause Apache for Windows is multithreaded, it does not use a separate process for each request, as Apache does with - Unix. Therefore, the process-management directives are different: - PA HREF=mod/core.html#startserversStartServers/A - This - tells the server how many processes to use. Unlike Unix, there - will never be more than this number, and only one will be used - at a time (the others will be held in reserve in case the main - processes crashes or otherwise dies). The recommended default is - CODEStartServers 3/CODE. + Unix. Instead there are usually only two Apache processes running: + a parent process, and a child which handles the requests. Within + the child each request is handled by a separate thread. + P + + So the process-management directives are different: PA HREF=mod/core.html#maxrequestsperchildMaxRequestsPerChild/A - Like the Unix directive, this controls how many requests a @@ -186,15 +184,15 @@ without recompiling the server. If Apache is compiled normally, it will install a number of optional modules in the CODE\Apache\modules/CODE directory. To activate these, or other - modules, the new A HREF=mod/mod_dll.html#loadmoduleLoadModule/A + modules, the new A HREF=mod/mod_so.html#loadmoduleLoadModule/A directive must be used. For example, to active the status module, use the following (in addition to the status-activating directives in CODEaccess.conf/CODE):/P PRE LoadModule status_module modules/ApacheModuleStatus.dll /PRE - PInformation on A HREF=mod/mod_dll.html#creatingcreating module - DLLs/A is also available./P + PInformation on A HREF=mod/mod_so.html#creatingcreating loadable + modules/A is also available./P LIPApache can also load ISAPI Extensions (i.e., Internet Server Applications), such as those used by Microsoft's IIS, and other Windows servers. A HREF=mod/mod_isapi.htmlMore information
