Disable automatic disabling of account when disk quota exceeded

[mart]

I want to prevent accounts from being disabled when they reach the disk usage quota. The idea is that I'll run a script to tell me who is over quota and I'll handle it through a separate process, but I don't want CPANEL taking any action itself.

I still want to set the quota on accounts so that the users can see that they do have a quota, so setting all accounts to unlimited is not an option.

Does anyone know whether there is a way of doing this via normal configuration settings?

If not, what modification to the CPANEL code would be required to implement it?

Thanks for any input.
Martin

 

[dalem]

cpanel does not atoumaticly suspend accounts that have reached their max quoata

 

[Gareth]

Do you mean bandwidth quota

 

[sh4ka]

If you mean Bandwidth quota:

Log in into your WHM, go to Tweak Settings, Notifications:
Disable Suspending accounts that exceed their bandwidth limit.

 

[mart]

Thanks for the responses. I'm actually talking about disk usage quota, not bandwidth quota.

I believe if an account goes over disk usage quota, any emails sent to any mailbixes in that account will bounce. Is this not the case? (I'm going by what someone else has told me, as I'm new to cpanel myself).

What happens if they are running an application that writes to the disk, either in files or a MySQL database, when they are over quota?

What I want is to ensure that the customer's services are not disrupted in any way, as this just leads to frustration and urgent support calls.

Can someone tell me definitively whether this is already the case, or whether I will need to implement some sort of mod to allow ininterrupted use past the disk quota.

Thanks
Martin

 

[chirpy]

*nix disk quotas are simple things. If you go over your quota you will not be able to write or create to files, it has nothing to do with cPanel. So, if email arrives for an over quota account, it will be lost/bounce/held in the queue depending on your configuration settings in WHM > Exim Configuration Editor. If they have a script that writes to files, the script will fail.

Simply, the user of the account is responsible for what happens if they go over quota and in that light they need to ensure that they have enough space for their needs. If that means having an excessively large quota, then that's it.

There's no way around that. It's the equivalent of running out of disk space, if there's no more space, things will break.