On 12.8.2014 13:04, Jochen Bern wrote:
On -10.01.-28163 20:59, Jiri Bourek wrote:
On 10.8.2014 06:18, Will Yardley wrote:
Depends on the environment; in many cases, the admin could, or may even be expected to, raise the quota.
If you're expected to raise the quota in case it's exceeded, don't set it in the first place, there is no point to it. Or - if you really want that exercise in futility - use quota_warning and raise it automatically.
Where exactly did you read "automatically"?
Users need reminders not to be disk hogs. Managers want to be asked before company resources get allocated. Sysadmins may want to verify that it's actually the *user* using the disk space and not some software or e-mail problem. Quotas and their getting exceeded provide a hook for all these (non computer-only) procedures, even if the quota eventually *does* get raised for all cases of proper need.
You can do all of those things as a reaction to quota_warning e-mail sent to you _before_ the account exceeds its quota. No need to hit the error path by actually exceeding the quota.