• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Limit Resources per domain

D

dprophit

Guest
Thank you for the call. To my understanding you are interested in establishing mysql and apache resource limits on a per user/vhost basis.

On the mysql side, this can be accomplished with the GRANT statement within mysql itself. see http://dev.mysql.com/doc/refman/5.0/en/grant.html

There are 3 resource limiting variables available for mysql 4.1:
| MAX_QUERIES_PER_HOUR count
| MAX_UPDATES_PER_HOUR count
| MAX_CONNECTIONS_PER_HOUR count

5.0 adds MAX_CONNECTIONS_PER_HOUR.

You can set these for all users with a clever INSERT statement, or via phpmyadmin.

Apache provides RLimitCPU, RLimitNPROC and RLimitMEM. These directives can be set on a global and per vhost basis. For more information: http://httpd.apache.org/docs/1.3/mod/core.html#rlimitcpu
Rackspace gave me the following advice. Now how to implement it? I saw even triggers but not sure how to use it. The documentation doesn't talk about the "user" to use. We have normal hosting accounts and high traffic accounts. We want to offer more resources to the higher paying customers.

I think Swsoft should build in resource limits per client and then build it into the API. Should not be hard to insert those values into the /conf/httpd.include once they are figured out. But we don't want to fill them in for every single client. Clients can create their own domains and have their own templates so we need to control it at the server level.

Who else wants this? :D
 
Back
Top