That's what the Services Status page is good for 
Also, if it is up and something is stuck, there is also the WebTools -> Debugger which could show Execute Requests that may be stuck, and you can re-initiate there by just clicking it. Sometimes clears it up for me if something is stuck there for whatever reason.
If you alter DNS settings directly to bind files, it will be overwritten with a reboot or modification done from the control panel that triggers the scripting. If you make a change directly, like with other config files either fully or partially controlled by i-mscp, you need to change them in /etc/imscp/(service name, ie. bind)/working
You can also make broad changes by modifying the /parts files or Perl scripts that handle these things. beauty of open source.
Hope that helps.
News on the boxbilling side... they have decided to completely open-source the app and donate it to the community. this is awesome news as it's a great starter platform, and I can't wait to see what the community at-large does with it. HostBill is dying because of the terrible direction of it's owner/developer in Poland, and WHMCS still has no good ordering system for clients. BoxBilling seems perfect, so it's exciting to see what could be possible as they open-source it completely.
It is fast, but it costs. I think Apache with php-fpm now is flexible and fast (lot of CPU usage though). And, Apache + Varnish has been shown to be almost as fast and sometimes faster than Litespeed caching. Putting Varnish in front of Apache on an i-MSCP server is pretty easy also. I could script it, but I'm not sure how to make it a plug-in, and getting some option controls of varnish in the control panel is a bit beyond me. But I can say that it's VERY fast. I have one site serving up millions of database queries a day and many thousands of pageviews with a separate database server.
I have not tried the Open Litespeed yet, so I don't know its performance. I'm usually weary of free version when they have a paid version, because they usually make the free version weak to make folks buy the paid version.
Use "top" or I like "htop" which you have to install, and sort by memory usage, and you will see what is really using the most memory. I install fully-used i-MSCP on 1GB VPS' often, and it really starts with no usage around 350MB, and goes up under a little load but maxing at 1GB for no reason is strange, so run "htop" and see what is using the memory.
I thought I had problems with the wordpress installer and php-fpm as far as permissions go, but looks like it was the issue you guys found and nuxwin posted about with the .htaccess files, just wanted to relay that here. have the other packages been installing correctly for everyone with php-fpm and latest master?
There are some threads in the Migration section of the forum with good information about migrating to a different server. It depends if you're keeping the same hostname and IP, or changing them, what will happen.
It basically involves taking a mysqldump, and copying of all /var/www/virtual/ files and /var/mail/ files.
Make the new server, install same i-mscp version and configuration. Stop i-mscp_daemon.
You take the mysqldump from the old server, and import it to the new server (backup the new server first, you need the debian-sys-maint password entry). Set all domains statuses to "change". If you changed the IP address or hostname, change those in the database as well.
Start i-mscp daemon, it should start creating all the domain directories, etc.
Make sure /etc/groups has all the right users and all the /var/www/virtual directories are there, then copy over all those /var/www/virtual files and /var/www/virtual files.
That's kind of a basic overview, there are a lot of things that can go wrong, or it could go smoothly, it depends on if you have custom configurations, etc.
Ubuntu 13.04 is released. For more information visit the website http://www.ubuntu.com/
anyone try running master branch on it yet?
nginx is supposed to handle requests faster than apache, and does. it also does (static file) caching and load balancing and other things. varnish is an accelerator, doing caching and can do load balancing as well. it can handle some extreme load. just an option, i find it the best accelerator with apache, nginx has benefits too. building it in as an option would just save time for config, but it's not much work anyway
dzchimp
hehe. I put Varnish in front of Apache often with i-MSCP, and it's pretty simple, change some apache files in i-mscp parts, and one or two bits in the perl script regarding the port change. not sure if it should be plug-in or i-mscp setup option, or anything. but it's a great performer
