From: davidsen@ariel.crd.GE.COM (william E Davidsen) Subject: Re: Disk Quotas (was Re: New feature for the filesystems.) Date: Thu, 15 Apr 1993 12:25:11 GMT
In article <9821@dirac.physics.purdue.edu>, bcr@bohr.physics.purdue.edu (Bill C. Riemers) writes:
| Yes I haven't seen a system yet that properly handles hard quotas. Most
| systems will still let you write to /tmp so you just direct the normal
| programs to put thier output to there and then take care of them before
| logging out.
You do realize that quotas are on a "per filesystem" basis? You might
have a quota on /tmp, and that would be different from the quota on the
home filesystem, etc. That's not remotely a bug, it's the way it was
intended to work.
And the reason for quotas is to protect the system, not to punish the
user from trying to use resources to get something done... I could see
having a soft limit on /tmp of about 100b (for shell history), and a
hard limit of 50MB, with a time limit of 1hr or so. That lets people get
enough disk to do image processing, and still encourages them to remove
files as soon as they are done.
Of course I usually run a daemon which encourages /tmp cleanliness,
too.
-- bill davidsen, GE Corp. R&D Center; Box 8; Schenectady NY 12345