From: Joshua Slive Date: Fri, 7 Jun 2002 02:54:37 +0000 (+0000) Subject: Remove a broken link. X-Git-Tag: 2.0.37~43 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=8943e3944fc7cd3ed3836efa97e999a1201ec601;p=apache Remove a broken link. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@95560 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mpm_common.html.en b/docs/manual/mod/mpm_common.html.en index 312379fc4c..fca1d7af10 100644 --- a/docs/manual/mod/mpm_common.html.en +++ b/docs/manual/mod/mpm_common.html.en @@ -311,15 +311,14 @@ requestsRefers to a user by their number. -

The user should have no privileges which result in it being - able to access files which are not intended to be visible to the +

The user should have no privileges that result in it being + able to access files that are not intended to be visible to the outside world, and similarly, the user should not be able to - execute code which is not meant for httpd requests. It is + execute code that is not meant for httpd requests. It is recommended that you set up a new user and group specifically for running the server. Some admins use user nobody, but - this is not always possible or desirable. For example - mod_proxy's cache, when enabled, must be - accessible to this user (see CacheRoot).

+ this is not always desirable, since the nobody user + can have other uses on the system.

Notes: If you start the server as a non-root user, it will fail to change to the lesser privileged user, and will instead diff --git a/docs/manual/mod/mpm_common.xml b/docs/manual/mod/mpm_common.xml index 2eb6f4d339..1156861215 100644 --- a/docs/manual/mod/mpm_common.xml +++ b/docs/manual/mod/mpm_common.xml @@ -584,16 +584,14 @@ requests

Refers to a user by their number.
-

The user should have no privileges which result in it being - able to access files which are not intended to be visible to the +

The user should have no privileges that result in it being + able to access files that are not intended to be visible to the outside world, and similarly, the user should not be able to - execute code which is not meant for httpd requests. It is + execute code that is not meant for httpd requests. It is recommended that you set up a new user and group specifically for running the server. Some admins use user nobody, but - this is not always possible or desirable. For example - mod_proxy's cache, when enabled, must be - accessible to this user (see CacheRoot).

+ this is not always desirable, since the nobody user + can have other uses on the system.

Notes: If you start the server as a non-root user, it will fail to change to the lesser privileged user, and will instead