From: Vlad (vlad_at_vlad.net)
Date: Sat 05 Jan 2002 - 21:47:37 GMT
Why bother with vserver to begin with? Give them a web interface to manage
their <VirtualHost> directives, chroot their ftp to their home directory,
use mod_rewrite to lock them out of other important directories and that
should do it as long as all 250 don't have different tastes - you're
usually better off splitting people with need for
php/cgi/frontpage/ssl/webdav.. If you pack all that in a single file
you'll be running out of ram very quickly.
I actually have it split 3 ways for about 400 servers; I have two virtual
servers for web (one apache w/ mod_php, other with frontpage for microsoft
people) and I have one vserver for sql that absolutely nobody seems to be
On Sat, 5 Jan 2002, Gil Vidals wrote:
> I've read the documentation for VServer and I need help in
> understanding the "best" way to set up 250 virtual servers on
> one linux box.
> I know I can have one httpd daemon per vserver and launch them
> like so:
> apache/httpd -d /vserver/one/httpd.conf
> apache/httpd -d /vserver/two/httpd.conf
> OR I can also have one httpd.conf file for all the VServers like
> <VirtualHost 220.127.116.11>
> <VirtualHost 18.104.22.168>
> In this second scenario, it won't be possible for each VServer
> owner to manage their own private httpd.conf file, but the
> advantage seems to be that there is only one httpd daemon
> running instead of 250.
> I would appreciate any comments or clarifications on the "best"
> way to set up 250 VServers on one box.
> Do You Yahoo!?
> Send FREE video emails in Yahoo! Mail!