No subject

7.16.
You shall at all times use Web Site Space exclusively as a conventional Web
Site. You shall not use the Web Site Space or Your Services in any way which
may result in an excessive load on the 1&1 Equipment, including but not
limited to installing or running web proxies, using your allotted space as
online backup or storage, or mirroring mass downloads. Use of Web Site Space
and Your Services shall be in a manner consistent with this Agreement and
shall not in any way impair the functioning or operation of 1&1's Equipment
or network. Should your use of the 1&1 Services result in an overly high
load on the 1&1 Equipment, in 1&1's sole discretion, 1&1 may suspend your
account until the cause of any such overload is determined and resolved.

14.4.
You further agree that in the event that 1&1 believes, in its sole
discretion, that you have breached any provision(s) of Section 7 of this
Agreement, or any of its subparts, by storing or allowing material such as
that described in the aforementioned Section 7, or any of its subparagraphs,
to be transmitted by 1&1's Equipment, that 1&1 may without any liability to
you, and in addition to any other remedies, erase or purge such materials
from 1&1's Equipment without prior notice to you.



I'd say that most, if not all hosting companies have some verbiage in their
TOS that allows them to disable and delete an account if it is abusing the
servers.  For a buck a month, I'm certainly going to shut down a blog that
has 10,000 readers and consistently puts a .3 load on a shared server.  Most
websites don't do that though.  The verbiage is there simply to let people
know that they shouldn't try to host kcci.com on a 1 dollar a month plan, or
try to use their site as an FTP dump.  I don't expect that I will
immediately delete any site that accidentally spikes the CPU due to
unexpected load, but I do want to have verbiage that lets me delete
iamagooglehacker.com from my server immediately when they try port scanning
all of googles servers from my datacenter.

-Matt


-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:cialug-bounces at cialug.org">cialug-bounces at cialug.org</a> [<a class="moz-txt-link-freetext" href="mailto:cialug-bounces at cialug.org">mailto:cialug-bounces at cialug.org</a>] On Behalf
Of Todd Walton
Sent: Wednesday, January 20, 2010 3:02 PM
To: Central Iowa Linux Users Group
Subject: Re: [Cialug] New hosting solution

On Wed, Jan 20, 2010 at 2:46 PM, Matt Breitbach
<a class="moz-txt-link-rfc2396E" href="mailto:matthewb at flash.shanje.com">&lt;matthewb at flash.shanje.com&gt;</a> wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">The policy of monopolizing CPU/Bandwidth/Memory is pretty standard across
all hosting platforms.&nbsp; If you look at anyone's TOS, it usually says
something very similar.&nbsp; We just decided not to bury it.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Including the deleting part?  I always thought standard procedure was
to throttle resource usage before it gets out of hand, not to ask
users to do it and then take drastic action when they mess up.

--
Todd
_______________________________________________
Cialug mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Cialug at cialug.org">Cialug at cialug.org</a>
<a class="moz-txt-link-freetext" href="http://cialug.org/mailman/listinfo/cialug">http://cialug.org/mailman/listinfo/cialug</a>


_______________________________________________
Cialug mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Cialug at cialug.org">Cialug at cialug.org</a>
<a class="moz-txt-link-freetext" href="http://cialug.org/mailman/listinfo/cialug">http://cialug.org/mailman/listinfo/cialug</a>
  </pre>
</blockquote>
</body>
</html>

--------------030500050307010607090502--