User may not:
- Use 25% or more of system resources for longer then 90 seconds. There are numerous activities that could cause such problems; these include: CGI scripts, FTP, PHP, HTTP, etc.
- Run stand-alone, unattended server-side processes at any point in time on the server. This includes any and all daemons, such as IRCD.
- Run any type of web spider or indexer (including Google Cash / AdSpy) on shared servers.
- Run any software that interfaces with an IRC (Internet Relay Chat) network.
- Run any bit torrent application, tracker, or client. You may link to legal torrents off-site, but may not host or store them on our shared servers.
- Participate in any file-sharing/peer-to-peer activities
- Run any gaming servers such as counter-strike, half-life, battlefield1942, etc
- Run cron entries with intervals of less than 15 minutes.
- Run any MySQL queries longer than 15 seconds. MySQL tables should be indexed appropriately.
- When using PHP include functions for including a local file, include the local file rather than the URL. Instead of include(“http://yourdomain.com/include.php”) use include(“include.php”)
- To help reduce usage, do not force html to handle server-side code (like php and shtml).
- Only use https protocol when necessary; encrypting and decrypting communications is noticeably more CPU-intensive than unencrypted communications.
The use of more than 250,000 inodes on any shared account may potentially result in a warning first, and if no action is taken future suspension. Accounts found to be exceeding the 100,000 inode limit will automatically be removed from our backup system to avoid over-usage, however databases will still be backed up. Every file (a webpage, image file, email, etc) on your account uses up 1 inode.
Sites that slightly exceed our inode limits are unlikely to be suspended; however, accounts that constantly create and delete large numbers of files on a regular basis, have hundreds of thousands of files, or cause file system damage may be flagged for review and/or suspension. The primary cause of excessive inodes seems to be due to users leaving their catchall address enabled, but never checking their primary account mailbox. Over time, tens of thousands of messages (or more) build up, eventually pushing the account past our inode limit. To disable your default mailbox, login to cPanel and choose “Mail”, then “Default Address”, “Set Default Address”, and then type in: :fail: No such user here.