I can't agree more, this is what I was discussing with their support following to the bad news :
https://blog.cloudlinux.com/mysql-governor-moving-from-all-to-abusers And, we are sent here to make hear our voices, does much people know about this voice site really, i think, it is like whmcs feedback site, talk, talk, talk, and we (CL team) do what we want
This a serious drawback with nothing equivalent in exchange. Unadapted for a shared hosting OS software
1. Settings in xml file are unfriendly, and limited for customization, it needs to be in UI.
2. The problem is that we are obliged to set highest limit of all plans for current and shorts (plan with 8 core) :
<limit current="801" long="200" mid="400" name="cpu" short="801"/>
So, the only solution is to be able to customize governor abuers limit based on packages.
As you know, any shared hsoting server sell different plans with dedicated ressources on a same server.
Hello,
I can't agree more, this is what I was discussing with their support following to the bad news :
https://blog.cloudlinux.com/mysql-governor-moving-from-all-to-abusers
And, we are sent here to make hear our voices, does much people know about this voice site really, i think, it is like whmcs feedback site, talk, talk, talk, and we (CL team) do what we want
This a serious drawback with nothing equivalent in exchange. Unadapted for a shared hosting OS software
1. Settings in xml file are unfriendly, and limited for customization, it needs to be in UI.
2. The problem is that we are obliged to set highest limit of all plans for current and shorts (plan with 8 core) :
<limit current="801" long="200" mid="400" name="cpu" short="801"/>
So, the only solution is to be able to customize governor abuers limit based on packages.
As you know, any shared hsoting server sell different plans with dedicated ressources on a same server.