zEitEr
Super Moderator
Hello,
I've noticed, that directadmin does not forbid to change hosting package even if a new package has less dedicated resources: ftp accounts, pop accounts, mysql databases, etc.
Let's user bob has a PKG-2 and uses 2 mysql DBs from 2 allowed, and 10 pop boxes from 20 allowed. And now if we decide to switch the package to another one, with allowed 1 mysql db and 6 email boxes, directadmin will allow to do that, and the user will be using old amounts of resources.
To avoid this situation, we forbid to change packages from our billing system, as the billing system that we use, does not take into consideration the current usage of resources.
That is not a good way out. So my wish would be to get this check implemented into one of the following DA's releases.
Of course it might be possible to figure out with user_modify_pre.sh (if it's called on package change and have all necessary variables).
I've noticed, that directadmin does not forbid to change hosting package even if a new package has less dedicated resources: ftp accounts, pop accounts, mysql databases, etc.
Let's user bob has a PKG-2 and uses 2 mysql DBs from 2 allowed, and 10 pop boxes from 20 allowed. And now if we decide to switch the package to another one, with allowed 1 mysql db and 6 email boxes, directadmin will allow to do that, and the user will be using old amounts of resources.
To avoid this situation, we forbid to change packages from our billing system, as the billing system that we use, does not take into consideration the current usage of resources.
That is not a good way out. So my wish would be to get this check implemented into one of the following DA's releases.
Of course it might be possible to figure out with user_modify_pre.sh (if it's called on package change and have all necessary variables).