Legal Notices
Resource Usage Policy

DigiServ™ provides our clients with Web Hosting accounts that permit the use of CGI files, PHP scripts, and other executable programs. Because these scripts use much more system resources than standard HTML pages, certain restrictions must be made governing the use of such "active content" systems. In most cases we are able to determine what specific script or application is causing the system resource to over-run.

Users may not, through a cron job, CGI script, interactive commands, or any other means, initiate the following on our servers:

  • Run any process that requires more than 32MB of memory space or 25% or more of system resources.
  • Use find anywhere except in their own directories.
  • The scripts may not interact with any server configuration or hardware. Accounts running these scripts are subject to immediate account termination without refund.
  • To help reduce usage, do not force html to handle server-side code (like php and shtml).
  • 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("") use include("include.php")
  • Send out mail to more than 300 addresses in one batch, whether sequentially or in parallel, not exceeding 100 recipients. Such batches must "sleep" for at least an hour between each delivery attempt.
  • The script can not be used or referenced from any other site not hosted by DigiServ™.
  • The script must execute in a timely fashion. Any script that uses the processor for more than 90 seconds is subject to removal.
  • Any script that appears to be designed specifically to attack or otherwise maliciously affect the server is completely unacceptable, and if such scripts are found on the account will be terminated immediately and your actions will be reported to the proper local, authorities and legal action will be taken to prosecute the account holder to the fullest extent of the law by DigiServ™.
  • Send or receive, through mail, any file larger than 100MB on our International servers and South African servers. This limit is enforced in our mail server software and cannot be set per individual domain name. If someone has to send an e-mail message larger than this limit, please inform them to use an alternate method such as FTP or placing the file on a web site for people to download. Otherwise, their mail will be rejected and potentially the sender blocked. Large messages coupled with long upload/download times bog down the mail server, use unnecessary mail server bandwidth, and cause long delays for people to download the message on the receiving end (especially if they're on dialup).
  • Run an interactive chat application.
  • Perl-based chat room scripts are strictly prohibited.
  • Scripts must be kept secure. Chmoding scripts to 777 is a violation of this policy. Keeping scripts in a publicly viewable directory (one without a index.html file) is also in violation of this policy.
  • Any accounts with scripts found in violation of these policies are subject to future scrutiny of all CGI, Perl, and PHP scripts by our System Administrators. If a script is found to be harmful to the system, it will be killed immediately and the account locked down until the account owners have been contacted. Malicious scripts are subject to immediate account termination without refund of any pre-paid monies.
  • Run a banner exchange, remotely accessible web counter, or any other services that perform CGI processes for sites outside our network.
  • Only use https protocol when necessary; encrypting and decrypting communications is noticeably more CPU-intensive than unencrypted communications.

CPU Usage

The CPU usage is subject to some regulations. Each hosting account can use up to 10% of the CPU power for no longer than 90 seconds at any given time, and/or 4.5% per 24 hours.

DigiServ™ strongly recommends that customers be very judicious when using the CPU power for their accounts. We reserve the right to block files or scripts that excessively use CPU. We may also suspend the Customer's account in the case of registered impact on other accounts on the server or disturbance caused to its functioning. If we do block or suspend an account, then its owner will be notified of the situation and given an explanation, and/or offered to upgrade to a dedicated or a semi-dedicated web hosting solution.


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. 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.

Important Note

Most of these restrictions are based on our other policies. The restrictions on mail delivery exist for a very simple reason: We run web servers, not mail servers. Processing large amounts of mail adversely affects web server performance. 

If we find that you are performing bulk mail runs, regardless of whether it is SPAM or not, we will have to put your account on hold for Abuse and investigate. Please send such mailings through your local ISP's mail server, or any other mail server which you are authorized to use. Many such mail servers are configured especially to handle an extremely high volume of mail. This is not applicable to dedicated server customers, providing that it does not interfere with DigiServ™’s ability to manage the server on the client’s behalf.

Why do we have this Policy?

A Virtual Server, also known as Shared Web Hosting, Email Hosting, Reseller Hosting and/or Unlimited Domains Hosting is shared. As such, there are many accounts per machine. In all fairness, DigiServ™ 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.

What happens if I violate this Policy?

All accounts that are found to using excessive amounts of system resources will receive an email warning from DigiServ™. This warning will inform you that there is too much CGI/PHP running and it will provide options for reducing the usage or upgrading your server. If you do not reduce the usage within 24 hours of the email being sent, your account will be cancelled.