| Home | Acceptable Use Policy | Terms & Conditions | UCE (SPAM) Policy | Privacy Policy |
Web Hosting Pod allows CGI to be used on all Virtual Servers. CGI can be resource intensive however, and because a Virtual Server must be shared with other users, we must limit how much of the CPU can be used by any one account on a shared server. There are several reasons why Web Hosting Pod has created its CGI Abuse policy for its virtual server users.
Any site whose CGI programs are using excessive amounts of system resources. Excessive amounts is defined as any amount that results in substantial degradation of server performance. Web Hosting Pod is the sole determinant of what constitutes degraded server performance.
Server Speed and Fairness to others
A Virtual Server is shared.
As such, there are many accounts per machine. In all fairness, Web Hosting Pod cannot allow one or two clients to use all of the System resources on a shared machine and have all other clients on the machine suffer because of it. Excessive CPU usage by one or more clients causes extreme slowness in all areas: FTP, Telnet, Web Sites and more. If the CPU usage gets too far out of hand, all sites hosted on the machine will return Errors and not be accessible in any way.Examples include, but are not limited to:
Flat File Database Driven Forums:
Due to their use of flat files instead of databases, Web Hosting Pod does not
allow the use of UBB or YABB bulletin boards. Use of these boards for large or
very active forums, results in system performance degradation, and cannot be
allowed in our shared server environment. Web Hosting Pod using VBulletin or
phpBB as a more efficient, database-driven alternative to these bulletin
boards. Busy sites with large forums and data bases are not suited to a shared
server environment.
Background Running Processes:
Background Daemons in general are prohibited on Web Hosting Pod servers,
including, but not limited to, IRC bots, eggdrop, BitchX, XiRCON, warez sites
and any other program that interferes with normal server operation.
Persistent mySQL Connections:
Due to the fact that persistent mySQL connections have the ability to use
considerable server resources, this configuration is not allowed on our shared
servers. It is understood that in some situations, persistent connections may
actually reduce resource usage on a server. However, we have found that
connections are commonly not released properly and are, therefore, more
detrimental to a shared hosting environment than they are helpful.
Cron Jobs:
We allow customers to set up cron jobs to perform routine functions
automatically. Due to the impact on the server, running some automated
processes can take up considerable server resources and in those cases, our
technicians may disable the cron job.
Mailing Lists:
We have a strict policy regarding use/spam on our network, but we do allow use
of mailing lists within the constraints of our
spam policy. However, sending thousands of e-mails off of a given server
can impact the performance of the server. Therefore we limit the amount of
e-mail allowed on our Shared Virtual Servers to no more than 1000
e-mails per day and 30 emails in 10 seconds.
Exploitable Scripts:
Unfortunately, many commonly used scripts can be exploited to allow
unauthorized users into our systems. Consequently we may on occasion need to
ban and consequently disable these scripts. You can view the most current
exploits under "Banned Scripts" below.
Other:
Other resource intensive scripts (depending on traffic) include but not
limited to:
- adcycle
Other applications that are prohibited on our
virtual servers include but are not limited to:
- offsite search engines
Unfortunately, many good things are turned on us to be used for nefarious activities. Commonly used scripts are frequently exploited to allow unauthorized access to the systems they are running on. Others just require more resources than is allocated on a shared server environment.
Consequently, in order to keep Web Hosting Pod network and servers safe, we may need to take actions that inconvenience our good customers. Any time we find scripts or other commonly used tools that can become easily compromised or impact other users by using too many server resources, we may need to disable scripts or other tools installed and used by our customers.
Whenever possible, we will notify our customers in advance. We will also attempt to keep this page updated with current scripts which will require removal from our shared servers and/or our network.
All trademarks are the property of their respective holders | |||||||||||||||||||||||||||||||||||||||||||||||||||