I've got a WebHost reseller account, which has unlimited bandwidth, and unlimited storage space.
I can create subAccounts with x,y and z bandwidth, space, and ftp accounts.
I dont have the time to manage it, but I am prepared to give someone the space for free, if they want to take the time to put together a community webspace of all the Community content.
The only thing I would advise everyone off, is that there are limitations in place to concurrency.
Meaning that it can only accomodate something like 15 concurrent client requests at any one time.
Arguably not an issue, as what are the chances that 15 people will be clicking on the same file, at exactly the same time.
Correction:
Limits are as follows
Memory Restriction
Our servers are hardened with a process memory restriction. A soft limit is set to 40 MB and a hard limit set to 64 MB. When a script uses over 64 MB of server RAM, it will show a 500 error. This restriction only applies for PHP and CGI scripts. Running a image file or static file shouldn't have any problem with this. After lots of analysis, we have found that, most of the scripts without any bugs works fine within the memory limit specified. If your script is not working, we highly suggest to optimize it and reduce the memory usage to run on our server. This restriction is purely applied to avoid sudden server load by a buggy php scripts.
max_user_connection Limit
In our all shared server max_user_connection for mysql has been set to 25. This is to prevent poorly coded php file injection and sql injection at certain time. This limit is a lot high comparing with shared resources. If you are receiving error says max_user_connection limit has been reached then you must be having some sql attack or injection. You should try enriching your security feature of your blog/forum/site.
allow_url_fopen limitation
allow_url_fopen() in php is disabled from all of our servers to protect abusive usage of php (Like Rapidshare premium link generator, rapidleech etc).
What is SOP (Suspension Overcome Period)?
SOP is a term we use to fix up the suspensions relating to our RAP (Resource Abuse Policy). If one of the account is suspended due to abusing the server resources (Like high load or memory), one can request to enable SOP mode for his account and fix the issue. When SOP mode is ON, that site can't be accessed through browser, while the user is able to login to Cpanel, FTP, Mysql to fix the issue up. As soon as the issue gets fixed, one can request to support to disable to SOP mode and get the account back to its old status. Please note, SOP mode is not eligible to be used for all types of account, but most of the accounts suspended for the reason of RAP, can have a resolution using SOP. In case, you need to access your site to fix the issue up, you need to let our abuse department know to enable the "SOP II" mode on your account, please note, we won't enable "SOP II" mode until you have a proper reason for that.
Modifié par Baaleos, 06 juillet 2012 - 12:30 .