cvs commit: apache-1.3 README.NT

1998-03-21 Thread pcs 
pcs 98/03/21 09:29:59

  Modified:.README.NT
  Log:
  Update NT information. Remove reference to StartServers. Document
  the single-child-process model slightly. Document the registry key and
  how it can be set.
  
  Revision  ChangesPath
  1.9   +37 -37apache-1.3/README.NT
  
  Index: README.NT
  ===
  RCS file: /export/home/cvs/apache-1.3/README.NT,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- README.NT 1997/10/27 20:22:18 1.8
  +++ README.NT 1998/03/21 17:29:59 1.9
  @@ -38,10 +38,11 @@
  the program to hook up to the Service Manager). On Windows 95
  it runs as a regular program.
   
  -3. It executes as multiple processes (this allows for some fault tolerance -
  -   if a server dies, another one takes its place. Also after dealing
  -   with a certain number of requests, each process voluntarily exits, to
  -   clean up any resources it might have forgotten to free up).
  +3. There is only ever one child process for handling requests.
  +   However for fault tolerance, if this process dies, another one
  +   takes its place. Also after dealing with a certain number of
  +   requests, each process voluntarily exits, to clean up any resources
  +   it might have forgotten to free up.
   
   By default Apache uses the directory \Apache for the ServerRoot ON THE
   DRIVE WHERE THE EXECUTABLE EXISTS. This can be changed with the -d
  @@ -49,29 +50,10 @@
   
   There are a couple of new directives:
   
  -ThreadsPerChild - Number of threads each server spawns)
  +ThreadsPerChild - Number of threads to use to handle requests
   ExcessRequestsPerChild  - Number of additional requests a server responds
  -  to, after it decides to exit
  -
  -Due to the behavior of NT when multiple processes have a socket open
  -for listening, I would recommend that you set the following in httpd.conf
  -(in the directory /usr/local/apache/conf):
  -
  -# Start up 3 servers (in case one dies, another can take its place, while
  -# a new one is spawned
  -StartServers 3
  -
  -# Don't force a server to exit after it has served some number of requests.
  -# If you do want server's to exit after they have run for a long time (to
  -# help the system clean up after the process), please set this to a pretty
  -# large number - like 10,000. What this will do, is, each child server will
  -# exit after serving 10,000 requests, and another server will take its place.
  -MaxRequestsPerChild 0
  -
  -# Number of concurrent threads at a time (set the value to more or less
  -# depending on the responsiveness you want and the resources you wish
  -# this server to consume).
  -ThreadsPerChild 20
  +  to, after it decides to exit (this is not
  +  currently used)
   
   Compilation
   ---
  @@ -96,11 +78,11 @@
   line.
   
   To build Apache within MSVC, you will need to build the following
  -projects and Makefiles, in the following order. Make sure that you
  -build the same configuration (i.e. Debug or Release) for all of the
  -various projects.
  +projects in this order. Make sure that you build the same
  +configuration (i.e. Debug or Release) for all of the various projects.
   
  -   regex/Makefile.mak
  +   regex/Makefile.dsp
  +   ap/ap.dsp
  os/win32/ApacheOS.dsp
  src/ApacheCore.dsp
  src/Apache.dsp
  @@ -118,24 +100,41 @@
   
   Apache can run as either a service (NT only) or a regular executable. 
   
  -To run as an executable, simply run \Apache\apache from the command
  +To run as an executable, simply run apache.exe from the command
   line. This will print the version number, then wait to serve
  -requests. To stop Apache, press Control-C to stop it running. Note
  +requests. If the server root is a directory other than \Apache, use
  +the -d option to give the correct server root, or store it in the
  +registry (see below).
  +
  +To stop Apache, press Control-C to stop it running. Note
   that there may be a delay between typing the command line and Apache
   being ready to accept requests as it checks the service manager. Use
   the -s option to prevent this delay.
   
  -To run as a service, first install the service with
  +When Apache starts it will look at the registry key
  +
  +  HKEY_LOCAL_MACHINE\Software\Apache Group\Apache\1.3 beta\ServerRoot
  +
  +to find the server root, unless specified by the -d command line
  +flag. The correct server root is stored in this key by the binary
  +installation, or when Apache is run with the -i option.
  +
  +To install Apache as a service on NT and set the server root registry
  +key, run
  +
  +  apache -i -d serverroot
   
  -  \Apache\apache -i
  +This will store the value of "serverroot" into the Apache ServerRoot
  +registry key, as above. Note that this can be used on both Windows NT
  +and Windows 95, however

cvs commit: apache-1.3 README.NT

1998-04-17 Thread pcs 
pcs 98/04/17 09:14:27

  Modified:.README.NT
  Log:
  Add some information about use of the binary installer in case we ever
  release a binary :-)
  
  Revision  ChangesPath
  1.10  +36 -4 apache-1.3/README.NT
  
  Index: README.NT
  ===
  RCS file: /export/home/cvs/apache-1.3/README.NT,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- README.NT 1998/03/21 17:29:59 1.9
  +++ README.NT 1998/04/17 16:14:27 1.10
  @@ -69,10 +69,13 @@
   
  nmake -f Makefile.nt installr
   
  -You cannot easily use a different installation directory. You can also
  -build debug versions of Apache, with the targets "_apached" and
  -"installd".
  +To specify a different install directory, use
   
  +   nmake -f Makefile.nt installr INSTDIR=c:\mydir
  +
  +You can also build and install debug versions of Apache, with the
  +targets "_apached" and "installd".
  +
   Make sure that before you run "nmake" that you've run VCVARS32.BAT
   so that your environment is configured to run nmake from the command
   line.
  @@ -92,8 +95,37 @@
   
   Installing a Binary Release
   ---
  +
  +Since this file is installed as part of the install process, you have
  +probably already figured out how to install the binary. But for
  +reference, here are the instructions:
  +
  +Run the Apache distribution file. This will ask for a location to
  +install Apache into (the default is \Program Files\Apache
  +Group\Apache), for a start menu name (default is Apache Web Server)
  +and for a choice of installations. The Typical installation installs
  +everything except the source code. The Minimum installations does not
  +install the manuals either. Choose Custom install if you want to
  +install the source code.
  +
  +After installation is completed, there are three new items on the
  +start menu. On NT you should run the "Install Apache as Service"
  +program, then start Apache as a normal service. On Windows 95 or if
  +you do not want to run Apache as a service, click on the "Apache
  +Server" option. This will start Apache running in a console window,
  +where it will print its version number, then wait to start serving
  +requests. The third start menu option accessing the manual, if it was
  +installed. If it was not installed, you can access the Apache manual
  +at the URL http://www.apache.org/.
  +
  +Once Apache is running (either in a console window, or as a service),
  +if you have not edited the configuration files, it will be listening
  +on port 80, so you can connect to it at this URL:
  +
  +  http://localhost/
   
  -The binary release is not yet available.
  +To configure Apache, go into the directory where you installed it and
  +edit the "httpd.conf" file in the "conf" directory. 
   
   Running Apache
   --

cvs commit: apache-1.3 README.NT

1998-05-30 Thread pcs 
pcs 98/05/30 05:57:48

  Modified:.README.NT
  Log:
  This file duplicated too much of windows.html. Refer people to
  that file for the details.
  
  Revision  ChangesPath
  1.11  +6 -150apache-1.3/README.NT
  
  Index: README.NT
  ===
  RCS file: /export/home/cvs/apache-1.3/README.NT,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- README.NT 1998/04/17 16:14:27 1.10
  +++ README.NT 1998/05/30 12:57:48 1.11
  @@ -28,157 +28,13 @@
   webserver performance are asked to compare against Apache on a Unix
   platform such as Solaris, FreeBSD, or Linux.
   
  -Changes for the Windows version
  
  +Installation or Compilation Instructions
  +
   
  -1. It is multithreaded
  -
  -2. It can run as a service (run apache -i to install the service)
  -   or as a regular program (run apache -s to avoid waiting for
  -   the program to hook up to the Service Manager). On Windows 95
  -   it runs as a regular program.
  -
  -3. There is only ever one child process for handling requests.
  -   However for fault tolerance, if this process dies, another one
  -   takes its place. Also after dealing with a certain number of
  -   requests, each process voluntarily exits, to clean up any resources
  -   it might have forgotten to free up.
  -
  -By default Apache uses the directory \Apache for the ServerRoot ON THE
  -DRIVE WHERE THE EXECUTABLE EXISTS. This can be changed with the -d
  -command line argument.
  -
  -There are a couple of new directives:
  -
  -ThreadsPerChild - Number of threads to use to handle requests
  -ExcessRequestsPerChild  - Number of additional requests a server responds
  -  to, after it decides to exit (this is not
  -  currently used)
  -
  -Compilation
  
  -
  -If you have downloaded the source code you will need to compile
  -it. This requires Microsoft Visual C++ version 5.0 or higher. 
  -
  -To compile Apache, run the command
  -
  -   nmake -f Makefile.nt _apacher
  -
  -in the src directory. To install Apache to the \Apache directory, run
  -
  -   nmake -f Makefile.nt installr
  -
  -To specify a different install directory, use
  -
  -   nmake -f Makefile.nt installr INSTDIR=c:\mydir
  -
  -You can also build and install debug versions of Apache, with the
  -targets "_apached" and "installd".
  -
  -Make sure that before you run "nmake" that you've run VCVARS32.BAT
  -so that your environment is configured to run nmake from the command
  -line.
  -
  -To build Apache within MSVC, you will need to build the following
  -projects in this order. Make sure that you build the same
  -configuration (i.e. Debug or Release) for all of the various projects.
  -
  -   regex/Makefile.dsp
  -   ap/ap.dsp
  -   os/win32/ApacheOS.dsp
  -   src/ApacheCore.dsp
  -   src/Apache.dsp
  -
  -Additional modules can also be built using project files in the os/win32
  -directory.
  -
  -Installing a Binary Release
  
  -
  -Since this file is installed as part of the install process, you have
  -probably already figured out how to install the binary. But for
  -reference, here are the instructions:
  -
  -Run the Apache distribution file. This will ask for a location to
  -install Apache into (the default is \Program Files\Apache
  -Group\Apache), for a start menu name (default is Apache Web Server)
  -and for a choice of installations. The Typical installation installs
  -everything except the source code. The Minimum installations does not
  -install the manuals either. Choose Custom install if you want to
  -install the source code.
  -
  -After installation is completed, there are three new items on the
  -start menu. On NT you should run the "Install Apache as Service"
  -program, then start Apache as a normal service. On Windows 95 or if
  -you do not want to run Apache as a service, click on the "Apache
  -Server" option. This will start Apache running in a console window,
  -where it will print its version number, then wait to start serving
  -requests. The third start menu option accessing the manual, if it was
  -installed. If it was not installed, you can access the Apache manual
  -at the URL http://www.apache.org/.
  -
  -Once Apache is running (either in a console window, or as a service),
  -if you have not edited the configuration files, it will be listening
  -on port 80, so you can connect to it at this URL:
  -
  -  http://localhost/
  -
  -To configure Apache, go into the directory where you installed it and
  -edit the "httpd.conf" file in the "conf" directory. 
  -
  -Running Apache
  ---
  -
  -Apache can run as either a service (NT only) or a regular executable. 
  -
  -To run as an executable, simply run apache.exe from the command
  -line. This will print the version nu

cvs commit: apache-1.3 README.NT

1998-09-20 Thread fielding 
fielding98/09/19 23:22:46

  Modified:.README.NT
  Log:
  Clean up some of the information and merge the warning from WARNING-NT.TXT.
  
  Revision  ChangesPath
  1.12  +33 -21apache-1.3/README.NT
  
  Index: README.NT
  ===
  RCS file: /home/cvs/apache-1.3/README.NT,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- README.NT 1998/05/30 12:57:48 1.11
  +++ README.NT 1998/09/20 06:22:46 1.12
  @@ -1,61 +1,73 @@
  -  Apache for Windows
  - Version 1.3 (and up)
  +Apache for Windows
  +   Version 1.3 (and up)
   
   What is it?
   ---
   
   Apache is an HTTP server, originally designed for Unix systems. This
  -is the first release of Apache for Windows systems.  Like the Unix
  -version, it includes many frequently requested new features, and has
  -an API which allows it to be extended to meet users' needs more
  -easily. It also allows ISAPI extensions.
  +is the first major release of Apache for Windows systems, including
  +Microsoft Windows NT, 98, and 95.  Like the Unix version, it includes
  +many frequently requested new features, and has an API that allows it
  +to be extended to meet users' needs more easily. It also allows ISAPI
  +extensions.
   
   Documentation
   -
   
   The documentation available as of the date of this release is also
  -included, in HTML format, in the htdocs/manual/ directory. For the
  -most up-to-date documentation, visit us on the WWW, at
  -http://www.apache.org/. For Windows specific information, see
  -http://www.apache.org/docs/windows.html.
  +included, in HTML format, in the <./htdocs/manual/> directory.
  +For the most up-to-date documentation, visit us on the WWW at
  +. For Windows specific information, see
  +.
   
   WARNING
   ---
   
  -Apache on NT has not yet been optimized for performance.  Apache still
  +Apache on Win32 has not yet been optimized for performance.  Apache still
   performs best, and is most reliable on Unix platforms.  Over time we
  -will improve NT performance. Folks doing comparative reviews of
  -webserver performance are asked to compare against Apache on a Unix
  +will improve performance for Windows NT. Folks doing comparative reviews
  +of webserver performance are asked to compare against Apache on a Unix
   platform such as Solaris, FreeBSD, or Linux.
   
  +Apache on Win32 should still be considered beta quality code.  It does not
  +meet the normal standards of stability and security that Unix releases do.
  +There is also a much greater chance of security holes being present in the
  +Win32 version of Apache, due to the frequent discrepancies between the public
  +documentation for the various Windows system calls and file system types
  +and the reality of what is included in Windows system software.
  +
   Installation or Compilation Instructions
   
   
  -See the file http://www.apache.org/docs/windows.html for details of
  +See the website  for details of
   how to install Apache from a binary release or how to compile Apache
  -from scratch. (This file is also available as
  -htdocs/manual/windows.html in either a source or binary distribution).
  +from scratch. This file is also included in the distribution as
  +<./htdocs/manual/windows.html>.
   
   Known Problems
   --
   
  +To get information about the current set of known problems, see our
  +online bug reporting database at .
  +In particular, search for problem reports under the category "os-windows".
  +
  +This is a rough list of what we know has not been implemented on Win32.
  +
   - The User directive is not supported. If you run apache as a service,
 you can change the user it runs as by going to 
 Control Panel->Services->Startup
   
   - suexec doesn't work
   
  -- RFC 1413 not yet ported
  +- RFC 1413 (IdentityCheck) is not yet ported
   
   - If you have a very busy server, when a server child process exits,
 any connections made to that child process that have not yet been
 accepted by it are aborted.
  -
  -- Problem with very long running cgi scripts (their output is garbled?)
   
  -- regex does not generate *.ih headers.
  +- The regex library build does not generate *.ih headers.
   
  -- Multithreadng is not properly abstracted
  +- Multithreading is not properly abstracted
   
   - htpasswd passwords are stored in plain text because Windows lacks a
 crypt() function

cvs commit: apache-1.3 README.NT

1998-10-03 Thread fielding 
fielding98/10/03 05:25:54

  Modified:.README.NT
  Log:
  Remove the bits that Ben Hyde objected to.
  
  Revision  ChangesPath
  1.13  +0 -4  apache-1.3/README.NT
  
  Index: README.NT
  ===
  RCS file: /home/cvs/apache-1.3/README.NT,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- README.NT 1998/09/20 06:22:46 1.12
  +++ README.NT 1998/10/03 12:25:53 1.13
  @@ -31,10 +31,6 @@
   
   Apache on Win32 should still be considered beta quality code.  It does not
   meet the normal standards of stability and security that Unix releases do.
  -There is also a much greater chance of security holes being present in the
  -Win32 version of Apache, due to the frequent discrepancies between the public
  -documentation for the various Windows system calls and file system types
  -and the reality of what is included in Windows system software.
   
   Installation or Compilation Instructions

cvs commit: apache-1.3 README.NT

1999-03-19 Thread pcs 
pcs 99/03/19 07:55:27

  Modified:.README.NT
  Log:
  Make the NT README more consistent with the standard README. Remove
  things which are not really relevant to someone reading this
  file after installing the pre-compiled binary (e.g. "Multithreading
  is not properly abstracted"). Remove <...> from around filenames and URLs.
  
  Revision  ChangesPath
  1.14  +66 -70apache-1.3/README.NT
  
  Index: README.NT
  ===
  RCS file: /export/home/cvs/apache-1.3/README.NT,v
  retrieving revision 1.13
  retrieving revision 1.14
  diff -u -r1.13 -r1.14
  --- README.NT 1998/10/03 12:25:53 1.13
  +++ README.NT 1999/03/19 15:55:26 1.14
  @@ -1,95 +1,91 @@
  -Apache for Windows
  -   Version 1.3 (and up)
   
  -What is it?
  
  + Apache
  + Version 1.3 (and up)
   
  -Apache is an HTTP server, originally designed for Unix systems. This
  -is the first major release of Apache for Windows systems, including
  -Microsoft Windows NT, 98, and 95.  Like the Unix version, it includes
  -many frequently requested new features, and has an API that allows it
  -to be extended to meet users' needs more easily. It also allows ISAPI
  -extensions.
  +  What is it?
  +  ---
   
  -Documentation
  --
  +  Apache is an HTTP server, originally designed for Unix systems. This
  +  is the version of Apache for Microsoft Windows NT, 98, and 95
  +  systems.  Like the Unix version, it includes many frequently
  +  requested new features, and has an API that allows it to be extended
  +  to meet users' needs more easily. It also allows ISAPI extensions.
   
  -The documentation available as of the date of this release is also
  -included, in HTML format, in the <./htdocs/manual/> directory.
  -For the most up-to-date documentation, visit us on the WWW at
  -. For Windows specific information, see
  -.
   
  -WARNING
  
  +  The Latest Version
  +  --
   
  -Apache on Win32 has not yet been optimized for performance.  Apache still
  -performs best, and is most reliable on Unix platforms.  Over time we
  -will improve performance for Windows NT. Folks doing comparative reviews
  -of webserver performance are asked to compare against Apache on a Unix
  -platform such as Solaris, FreeBSD, or Linux.
  +  Details of the latest version can be found on the Apache HTTP
  +  server project page under http://www.apache.org/.
   
  -Apache on Win32 should still be considered beta quality code.  It does not
  -meet the normal standards of stability and security that Unix releases do.
  +  Documentation
  +  -
   
  -Installation or Compilation Instructions
  -
  +  The documentation available as of the date of this release is
  +  also included, in HTML format, in the htdocs/manual/ directory.
  +  For the most up-to-date documentation can be found on
  +  http://www.apache.org/docs/. For Windows specific information, see
  +  http://www.apache.org/docs/windows.html.
   
  -See the website  for details of
  -how to install Apache from a binary release or how to compile Apache
  -from scratch. This file is also included in the distribution as
  -<./htdocs/manual/windows.html>.
  +  WARNING
  +  ---
   
  -Known Problems
  ---
  +  Apache on Win32 has not yet been optimized for performance.  Apache
  +  still performs best, and is most reliable on Unix platforms.  Over
  +  time we will improve performance for Windows NT. Folks doing
  +  comparative reviews of webserver performance are asked to compare
  +  against Apache on a Unix platform such as Solaris, FreeBSD, or
  +  Linux.
   
  -To get information about the current set of known problems, see our
  -online bug reporting database at .
  -In particular, search for problem reports under the category "os-windows".
  +  Apache on Win32 should still be considered beta quality code.  It
  +  does not meet the normal standards of stability and security that
  +  Unix releases do.
   
  -This is a rough list of what we know has not been implemented on Win32.
  +  Installation
  +  
   
  -- The User directive is not supported. If you run apache as a service,
  -  you can change the user it runs as by going to 
  -  Control Panel->Services->Startup
  +  If you have installed Apache as a pre-compiled binary, you can
  +  now run the server by selecting "Start Apache as console app"
  +  from the Start menu. You can configure Apache for your system
  +  by editing the file conf/httpd.conf in the directory where you
  +  installed Apache.
   
  -- suexec doesn't work
  +  See the http://www.apache.org/docs/windows.html