The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: alan@alanlee.org
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Quotas - did anyone ever use them?
Date: Thu, 30 May 2019 21:36:36 -0400	[thread overview]
Message-ID: <3ab907e0bdf1be98c1c628ce3957b415@alanlee.org> (raw)
In-Reply-To: <975B93B6-AD7C-41B5-A14D-2DE4FEFAD3A6@kdbarto.org>


My story is similar to most others here.  University of Arkansas in the 
early 90s enabled user disk quotas on the public access UNIX system - a 
SPARCserver 2000 with 10 CPUs and gobs of disk.  Each quota limit was 
far higher than (total disk space) / (# user accounts).  But each of the 
17K students at the time was automatically provisioned an account during 
registration.  So it became a bit necessary to impose a limit - even if 
one 98% of users would never come close to.

The dedicated college of engineering UNIX system was also a similarly 
equipped SPARCserver 2000 and did not enforce any quotas.  Unless the 
sys-admin yelling in the hallway at the povray guy eating 100% x 10 CPUs 
was technically a throttle / quota system.  He was efficient too.  
Zero'd in on the lab and workstation number by IP address and would be 
over your shoulder in less than 10K ms if you were acting a fool!

-Alan



On 2019-05-30 09:49, David wrote:
> I think it was BSD 4.1 that added quotas to the disk system, and I was
> just wondering if anyone ever used them, in academia or industry. As a
> user and an admin I never used this and, while I thought it was
> interesting, just figured that the users would sort it out amongst
> themselves. Which they mostly did.
> 
> So, anyone ever use this feature?
> 
> 	David

  parent reply	other threads:[~2019-05-31  1:45 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30 13:49 David
2019-05-30 14:23 ` Diomidis Spinellis
2019-05-30 14:26 ` Dan Cross
2019-05-30 14:27 ` Rico Pajarola
2019-05-31  7:16   ` George Ross
2019-05-30 14:29 ` Robert Brockway
2019-05-30 14:34 ` Theodore Ts'o
2019-05-30 14:48   ` John P. Linderman
2019-05-30 14:57     ` Jim Geist
2019-05-30 14:55 ` Andreas Kusalananda Kähäri
2019-05-30 15:00 ` KatolaZ
2019-05-30 17:28 ` Grant Taylor via TUHS
2019-05-30 19:19 ` Michael Kjörling
2019-05-30 20:42 ` Warner Losh
2019-05-30 22:23   ` George Michaelson
2019-05-31  1:36 ` alan [this message]
2019-05-31 19:07 ` Pete Wright
2019-05-31 20:43   ` Grant Taylor via TUHS
2019-05-31 20:59     ` Pete Wright
2019-06-01  0:30 ` reed
2019-06-04 13:50 ` Tony Finch
2019-05-30 16:04 Noel Chiappa
2019-05-30 16:48 ` KatolaZ
2019-05-30 17:42   ` ron
2019-05-31  0:21 Nelson H. F. Beebe
2019-05-31  0:37 ` Larry McVoy
2019-05-31  0:42 ` Arthur Krewat
2019-05-31 15:05   ` Nelson H. F. Beebe
2019-05-31 16:06     ` Michael Kjörling
2019-05-31 16:15       ` Grant Taylor via TUHS
2019-05-31 16:38         ` Michael Kjörling
2019-05-31 15:55   ` Rico Pajarola

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3ab907e0bdf1be98c1c628ce3957b415@alanlee.org \
    --to=alan@alanlee.org \
    --cc=tuhs@tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).