From: Astrid Malo Date: Tue, 17 Dec 2002 22:15:34 +0000 (+0000) Subject: Corrections include: X-Git-Tag: pre_ajp_proxy~2394 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=0763a88a6f057e3dd01b2a807776c226d419e231;p=apache Corrections include: - a couple of grammatical issues fixed - use term "change privileges" instead of "read/write/delete" just like NT/2000 does - fixed System to LocalSystem Submitted by: Iikka Meril�inen git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@98004 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/platform/windows.html.en b/docs/manual/platform/windows.html.en index d5d6a1755c..1c265c10c2 100644 --- a/docs/manual/platform/windows.html.en +++ b/docs/manual/platform/windows.html.en @@ -377,8 +377,8 @@

Never grant any network privileges to - the System account! If you need Apache to be able to - access network resources, create a separate account for Apache as + the LocalSystem account! If you need Apache to be able + to access network resources, create a separate account for Apache as noted below.

You may want to create a separate account for running Apache @@ -404,7 +404,7 @@ and script folders (htdocs and cgi-bin for example). -

  • Grant the account read/write/delete (RWXD) rights to the +
  • Grant the account change (RWXD) rights to the Apache logs directory.
  • Grant the account read and execute (RX) rights to the @@ -414,10 +414,10 @@
    It is usually a good practice to grant the user the Apache service runs as read and execute (RX) access to the whole Apache2 directory, except the logs subdirectory, where the - user has to have read/write/delete (RWXD) rights.
    + user has to have at least change (RWXD) rights.

    If you allow the account to log in as a user and as a service, - then you can log in yourself and test that the account has the + then you can log on with that account and test that the account has the privileges to execute the scripts, read the web pages, and that you can start Apache in a console window. If this works, and you have followed the steps above, Apache should execute as a service @@ -425,12 +425,14 @@

    Error code 2186 is a good indication that you need to review the "Log On As" configuration for the service, - since Apache cannot access a required network resource.
    + since Apache cannot access a required network resource. Also, pay + close attention to the privileges of the user Apache is + configured to run as.

    When starting Apache as a service you may encounter an error message from the Windows Service Control Manager. For example, if you try to start Apache by using the Services applet in the - Windows Control Panel you may get the following message:

    + Windows Control Panel, you may get the following message:

    Could not start the Apache2 service on \\COMPUTER
    @@ -692,8 +694,9 @@

    Apache should respond with a welcome page and a link to the Apache manual. If nothing happens or you get an error, look in the error.log file in the logs subdirectory. - If your host is not connected to the net, you may have to use this - URL:

    + If your host is not connected to the net, or if you have serious + problems with your DNS (Domain Name Service) configuration, you + may have to use this URL:

    http://127.0.0.1/ @@ -703,10 +706,10 @@ properly by editing the files in the conf subdirectory. Again, if you change the configuration of the Windows NT service for Apache, first attempt to start it from the command line to - assure that the service starts with no errors.

    + make sure that the service starts with no errors.

    Because Apache cannot share the same port with - another TCP/IP application, you may need to stop or uninstall + another TCP/IP application, you may need to stop, uninstall or reconfigure certain other services before running Apache. These conflicting services include other WWW servers and some firewall implementations.

    diff --git a/docs/manual/platform/windows.xml b/docs/manual/platform/windows.xml index 409b447a66..495f100324 100644 --- a/docs/manual/platform/windows.xml +++ b/docs/manual/platform/windows.xml @@ -363,8 +363,8 @@

    Never grant any network privileges to - the System account! If you need Apache to be able to - access network resources, create a separate account for Apache as + the LocalSystem account! If you need Apache to be able + to access network resources, create a separate account for Apache as noted below.

    You may want to create a separate account for running Apache @@ -390,7 +390,7 @@ and script folders (htdocs and cgi-bin for example).

    • -
  • Grant the account read/write/delete (RWXD) rights to the +
  • Grant the account change (RWXD) rights to the Apache logs directory.
  • Grant the account read and execute (RX) rights to the @@ -400,10 +400,10 @@ It is usually a good practice to grant the user the Apache service runs as read and execute (RX) access to the whole Apache2 directory, except the logs subdirectory, where the - user has to have read/write/delete (RWXD) rights. + user has to have at least change (RWXD) rights.

    If you allow the account to log in as a user and as a service, - then you can log in yourself and test that the account has the + then you can log on with that account and test that the account has the privileges to execute the scripts, read the web pages, and that you can start Apache in a console window. If this works, and you have followed the steps above, Apache should execute as a service @@ -411,12 +411,14 @@ Error code 2186 is a good indication that you need to review the "Log On As" configuration for the service, - since Apache cannot access a required network resource. + since Apache cannot access a required network resource. Also, pay + close attention to the privileges of the user Apache is + configured to run as.

    When starting Apache as a service you may encounter an error message from the Windows Service Control Manager. For example, if you try to start Apache by using the Services applet in the - Windows Control Panel you may get the following message:

    + Windows Control Panel, you may get the following message:

    Could not start the Apache2 service on \\COMPUTER
    @@ -678,8 +680,9 @@

    Apache should respond with a welcome page and a link to the Apache manual. If nothing happens or you get an error, look in the error.log file in the logs subdirectory. - If your host is not connected to the net, you may have to use this - URL:

    + If your host is not connected to the net, or if you have serious + problems with your DNS (Domain Name Service) configuration, you + may have to use this URL:

    http://127.0.0.1/ @@ -689,14 +692,14 @@ properly by editing the files in the conf subdirectory. Again, if you change the configuration of the Windows NT service for Apache, first attempt to start it from the command line to - assure that the service starts with no errors.

    + make sure that the service starts with no errors.

    Because Apache cannot share the same port with - another TCP/IP application, you may need to stop or uninstall + another TCP/IP application, you may need to stop, uninstall or reconfigure certain other services before running Apache. These conflicting services include other WWW servers and some firewall implementations.

    - \ No newline at end of file +