Quote:
Originally Posted by split_joel
The thing is with our plans we have things setup so situations like this do not happen. We have multi virtual and shared servers all which are quad xeons with atleast 4 gigs of ram. Our plans are setup so you can only use a certain amount of bandwidth and disk space so things like this don't happen. This is also why we have more then one virtual and shared server so if a client is using to many resources we can move them to another box.
|
Joel, this has nothing to do with how much bandwidth or disk space someone is using on their virtual account. The issue in the thread is that the customer was using too many server cpu resources to run his blogs. It was never said, and can be assumed that he was well within his bandwidth and disk space allotment. Someone could easily come along and kill a Quad Xeon, 4 gig ram with 100 blogs each doing constant crontab/rss updates and still only use 1000mb of space and push 5 gigs of transfer a month. It mostly depends on how a customer chooses to setup his/her software.
One thing I can offer is for hosts to install mod_throttle and mod_cpu (both will work with Apache 1.3) They will have to be adminstered through the root (no fancy Cpanel/WHM gui) but can help out somewhat. Google the 2 and you will find out more info on the two programs. Chaze you might want to use that too. Mod_CPU is very buggy from what Shawn (toonpornblog here on gfy) tells me, but Mod_Throttle will actually limit individual users apache sessions if set up correctly.
Hope that helps
Jim