Well I don't think I want different OS's.
It is probably the first option, I am just doing research on it, since someone had mentioned it to me, but they didn't give me much info on it.
I would like to know what the advantages of the first option might be? Right now I am unsure of my set up, but I do know that I have several domains under one server. I think maybe the person was talking about allocating certain amount of resources on a per site basis, that way "siteb" when it reaches so much traffic, it won't crash "sitea".
Main Topics
Browse All Topics





by: mchkorgPosted on 2008-08-08 at 01:29:05ID: 22188246
Hi,
might all point to the same IP. Then Virtual Hosts sorts the requests
cs/2.2/vho sts/
Is your goal to have several web sites (apache instances, let say) on a single server or to have several OSes on a single server ?
If first case (which I understood from your question), you should be talking of "virtual hosts". It means the possibility to have several website (ie, domain names) pointing to the same apache instance.
It's quite easy to set it up, please find some examples below. Basically, you say "if someone access my IP by entering the URL some.name.com, then redirect him to this particular website, meaning, directory structure. If someother.name.com, then this different directory structure)
To set it up, you'll have to manage your DNS zones correctly, especially if several www.something.com points to the same IP. Be careful, www.something.com might point to a different IP from something.com. And many www.differenthostnames.com
Be careful about overload problems. If you have tons of users, merging everythin to one a single server might be a problem
Check this: http://httpd.apache.org/do
If I'm totally wrong - and you are talking about virualizing OSes, tell me :)
Select allOpen in new window