Welcome, Guest. [ Log In ]
Question   What is your persistent (background) process policy?
Search KBase

Top 4 in this Area:
1. How do I set up a cron job?
2. What is a cron job?
3. May I run a cron job?
4. What is your persistent (background) process policy?

What is your persistent (background) process policy?
We define persistent/background processes as any unix user's command running non-interactively. That is, it runs while you aren't actively sitting there interacting with it through a shell window.

Firstly, we reserve the right to kill any user process on a shared server without warning or prior notification at our discretion.

We don't just do this capriciously though! We do this if the process is in any way adversely affecting the smooth functioning of your shared server. Of course if you have a dedicated server you can run whatever (LEGAL) processes you'd like, you should just be prepared for the consequences they may have on your machine.

  • IRC-related persistent processes of any kind (including, but not limited to, bots, bouncers, etc.) are STRICLY PROHIBITED, and are in violation of our TOS.
  • BitTorrent-related processes are not allowed.
  • Streaming Audio or Video servers of any kind are not allowed on shared hosting servers.
  • Running programs via cron is allowed provided you don't use excessive system resources.
  • If you want to set something up and have any questions just ask our friendly tech support team, they don't bite. :)

    Last updated: Jan 27, 2005.

    User Post (2006-01-04 19:29:08 by dmmaus)
    I asked tech support the following:
    > This could be interpreted to mean that an interactive IRC session
    > (where I'm sitting at an SSH terminal chatting with people, not
    > running a bot) is okay. But before I do so, can you please tell me if
    > my interpretation is correct, or if an interactive IRC session using
    > ircII is also against the TOS?

    And received this response:
    This is definately a gray area in our TOS. It doesn't sound like it will
    be a problem as long as the process is not taking up an abnormal amount
    of resources, but we do reserve the right to kill/disable any process
    that we believe is using an unfair amount of resources.

    Just thought I'd post it here in case anyone else is wondering if interactive IRC sessions are okay or not.
    User Post (2005-11-03 07:53:54 by vxjasonxv)
    Use non-persistent process trackers.
    Things like TorrentBits or whatever it's called are all PHP/Form based communication similar to XML-RPC communication through PHP files.
    User Post (2005-10-27 13:22:03 by lankantorrents)
    Ask nicely and they will give you permission to run a bittorrent tracker. Ofcourse all content should be 100% legal and you will have to convince them of that fact.

    Reply from DreamHost:
    You can install a bittorrent tracker if you'd like. However please note
    that you'll need to use it to distribute only material to which you own
    the copyright.And of course we reserve the right to disable your
    tracker if it begins to use an unreasonable amount of system resources,
    just as we would with any other CPU-intensive script.
    User Post (2005-09-28 08:11:22 by setral)
    pstarr, again as they mentioned if you paid for your own dedicated server, they'd let you do whatever you wanted, but doing that on a shared server could cause problems.
    User Post (2005-09-22 19:11:30 by pstarr)
    It occurred to me that one way to put my criminally-underused dreamhost account to use would be to run a TinyMUSH server for me and my friends to mess around on; very small-scale.

    The answer? No. Here's the original letter from tech support:

    Unfortunately, I'm afraid that for various administrative reasons we do
    not allow the use of persistent processes (ie. servers or "daemons") on
    our shared hosting servers. While your MUSH may be relatively secure,
    when the server you are on hosts as many other customers as it does the
    addition of a persistent process of this type just adds too many
    variables to the mix (stability, performance, and security related - not
    to mention other aspects, ie. bandwidth tracking). I'm sorry, but in
    order to run something like this we would require it to be placed on a
    dedicated server.

    I feel that requests like mine could be accommodated; I'd even be willing to pay a slight premium for the privilege, but Dreamhost feels differently. That's okay, the rest of their services is so good I can't get too worked-up about this.