Does adding a virtual host *require* a service restart?

[joe]

I'm pondering how to build an application where by new sites are spawned off of the parent domain for example:

"http:www.localhost" will now include

"http:anothersite.localhost" and maybe

"http:3rdsite.localhost"

Using litespeed I can imagine scripting this out, but I'm concerned it would require a service restart to activate the new virtual hosts and associate them with a listener. Is this true? If so I'm concerned how this would impact current connections to users as new VHs are added. Realistically it won't be often but I'm wondering still.

Can anyone suggest for better method to achive the same result? Using virtual hosts is not a requirement, just my first idea of how to achieve the goal.

I have full control of the web and local dns servers as well such that name resolution canl be updated as needed.

 

[mistwang]

Hi Joe,

Restarting litespeed server will not cause any service interuption.

If you want to avoid restart, you can configure only one vhost and use mod_rewrite if configuration for all of your sub domains are similar, like only document root is different.

Using dedicated vhost configuration should give you better security though.

Using vhost template is highly recommended for mass hosting as well.

 

[joe]

Thanks,

I was a little concerned that other sessions would be significantly interupted even though I don't expect heavy traffic. Shortly after posting this I read another thread here where you referred the poster to Dynamically configured mass virtual hosting with Apache, and this is very much along the lines of what I'm attempting to do here.

I don't suppose anyone has already written & posted the backend scripts to automate the process of creating the new files/folders on disk and updating the litespeed conf have they? If not thats my next task is writting that.

Thanks again for making an excellent product btw! I've recommended it to several friends.

 

[mistwang]

I was a little concerned that other sessions would be significantly interupted even though I don't expect heavy traffic.

All requests currently being processed will be finished as normal. Yes, service restart will need to start a new server instance and process configuration file, but the load introduced by it is minimum, should not be a big impact to the service speed.

I don't suppose anyone has already written & posted the backend scripts to automate the process of creating the new files/folders on disk and updating the litespeed conf have they?

I am afraid not, at least it is not published if some one did that already.

Thanks again for making an excellent product btw! I've recommended it to several friends.

Thanks!