You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2002/08/22 20:18:36 UTC
DO NOT REPLY [Bug 11944] New: -
Recommendations for Virtual Hosts
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11944>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11944
Recommendations for Virtual Hosts
Summary: Recommendations for Virtual Hosts
Product: Apache httpd-1.3
Version: 1.3.26
Platform: All
URL: http://www.axis9.com
OS/Version: All
Status: NEW
Severity: Enhancement
Priority: Other
Component: Other
AssignedTo: bugs@httpd.apache.org
ReportedBy: rhopek@axis9.com
I currently use Apache to provide hosting to many customers in a shared
environment. The one big feature that Apache is lacking for this scenario (at
least I haven't found a way to do it) is to have each virtual host run under a
separate user tied to the respective client's account.
Currently when you view the processes, you just see many httpd processes
running, all under the user 'nobody'. This unfortunately makes it difficult to
troubleshoot what users are generating unusually high loads. If each of those
process were running under distinguishable ids, my problem would be solved.
Thanks for listening.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org