Since I was under the burden of some distributed layer 7 attack I thought it might be a good moment to try and activate the CPU limit for the first time. On my 8-core CPU I have set the limit at 400% for a single user on my multi-user server. It's rather difficult to monitor how this actually works but I tried reading the CMD_ADMIN_LIMITS which seem to suggest that it is doing... something. The limited users website became practically unreachable, which is to be expected. Meanwhile, other website where still reachable so I figured it worked. Even though I expected more the see in my 1 minute load.
But then I noticed this plain HTML file in my /var/www/html folder seemed to become unreachable whenever the limited user seemed to run out of juice. How is this possible? The HTML file has nothing to do with any user and only serves as a monitoring file to check if the server is alive. Shouldn't this be running on the webapps users account or something?
Another thing is that I couldn't find any good information on how fast a new limit will become active. When I change the users CPU limit through the controlpanel does the limit activate instantly or do I need to wait a minute, maybe even reboot the webserver or the complete server?
My server is running Debian 12 with Directadmin 1.704.
But then I noticed this plain HTML file in my /var/www/html folder seemed to become unreachable whenever the limited user seemed to run out of juice. How is this possible? The HTML file has nothing to do with any user and only serves as a monitoring file to check if the server is alive. Shouldn't this be running on the webapps users account or something?
Another thing is that I couldn't find any good information on how fast a new limit will become active. When I change the users CPU limit through the controlpanel does the limit activate instantly or do I need to wait a minute, maybe even reboot the webserver or the complete server?
My server is running Debian 12 with Directadmin 1.704.