From: s_fuller@iastate.edu (Steve Fuller) Subject: Re: Disk Quotas (was Re: New feature for the filesystems.) Date: Thu, 15 Apr 1993 01:40:52 GMT
In <9821@dirac.physics.purdue.edu> bcr@bohr.physics.purdue.edu (Bill C. Riemers) writes:
>In article <C5HMw4.1vI@crdnns.crd.ge.com> davidsen@crd.ge.com (bill davidsen) writes:
>> I've never seen space deleted for you, you just can't write until you
>>get down below soft limit. Of course that may be an option, but I've not
>>found it in the docs. The sysadm is usually the dark force, through
>>scripts.
>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. For the few systems that I've seen that aren't fooled by
>placing the file in /tmp, they are fooled if you do a chown on the file
It would seem to me, from a new sysadmin standpoint, to have
anyone but root able to use chown. At least that's how it's done
here on the Ultrix systems at our site. Our system works as
follows as far as quotas:
1) If the file is in the middle of a write when you exceed your
quota, the file will be written in its entirety and not
truncated. Any furthur write requests will be denied
If you don't have any disk space when you start writing a file,
you will be told you have exceeded the quota.
>before you exceed your quota. Installing a hard quota is by no means a
>simple task. For the most part, if you are using a file system that reserves
>space for root, these shouldn't be neccissary.
> Bill
-- ==================================================== Steve Fuller = s_fuller@iastate.edu = No witty quote here yet... ===================================================