Return-Path: Mailing-List: contact docs-help@httpd.apache.org; run by ezmlm Delivered-To: mailing list docs@httpd.apache.org Received: (qmail 50266 invoked from network); 14 Dec 2002 18:38:56 -0000 Received: from unknown (HELO pizza-033.intraserver.de) (213.139.76.68) by daedalus.apache.org with SMTP; 14 Dec 2002 18:38:56 -0000 Received: (qmail 3634 invoked from network); 14 Dec 2002 18:38:57 -0000 Received: from p3e9d0292.dip0.t-ipconnect.de (HELO files) (62.157.2.146) by yetkin.de with SMTP; 14 Dec 2002 18:38:57 -0000 Subject: Re: [PATCH][RESEND] windows.xml rewrite From: Astrid Kessler References: Organization: Kess-Net User-Agent: Xnews/L5 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable To: docs@httpd.apache.org Message-ID: Date: Sat, 14 Dec 2002 19:36:54 +0100 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > Oh darn... but here comes a diff between two Unix versions of the > file. :-)=20 It's very easy to read. Nice work.=20 I've only some small suggestions. Could you check them and send a further= =20 patch? I'll commit this if Bill Rowe or others have no further comments. Section "Customizing Apache for Windows": 1) ... See the Apache documentation for all the available directives. -> ... See the directive index for all the available directives. and link directly to this file. Section "Running Apache as a service": 2)

By default, all Apache services are registered to run as user System (the LocalSystem account). The System account has no privileges to your network via any Windows-secured mechanism, including the file system, named pipes, =20 DCOM, or secure RPC. It has, however, wide privileges locally.

Do note mark "system" as code, because the account name is not "System" but= =20 "LocalSystem". Ok, this is only a little markup issue. Probaly you want to= =20 write: ->

By default, all Apache services are registered to run as system=20 user (the LocalSystem account). The LocalSystem account has no privileges to your network via any Windows-secured mechanism, including the file system, named pipes, =20 DCOM, or secure RPC. It has, however, wide privileges locally.

Section "Running Apache as a Consol=EA Application": 3) You can also run Apache via the shortcut Start Apache in Console placed= =20 to Start Menu --> Programs --> Apache HTTP Server 2.0.xx --> Control=20 Apache Server during the installation. This will open a console window= =20 and start Apache inside it. The window will remain visible until you=20 stop Apache. The Windows stays open only if Apache is not installed as a service.=20 Otherwise this menu entry starts the service and closes the console window.= =20 (Tested on Windows 2000) 4) If you don't specify a configuration file with -f or -n, Apache will=20 use the file name compiled into the server, such as conf\httpd.conf, = =20 relative to the path specified by the ServerRoot directive. Maybe I'm missing something. But the sentence is mistakable. One could=20 read: the configuration file is relative to the ServerRoot directive. This= =20 could never be because the configuration file must be found and read before= =20 apache is able to notice the ServerRoot directive.=20 5) You are often using
  • ....

  • . Is this intended? Imho
  • ...
  • is also ok. Section "Testing the Installation": 6)=20 After starting Apache (either in a console window or as a service) it=20 will be listening on port 80 (unless you changed the Listen directive in= =20 the configuration files). -> After starting Apache (either in a console window or as a service) it = =20 will be listening on port 80 (unless you changed the Listen directive in= =20 the configuration files or installed apache only for the current user).