The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Diomidis Spinellis <dds@aueb.gr>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Quotas - did anyone ever use them?
Date: Thu, 30 May 2019 10:23:48 -0400	[thread overview]
Message-ID: <f7d3a1e3-488b-6abf-a041-ad682b82bb16@aueb.gr> (raw)
In-Reply-To: <975B93B6-AD7C-41B5-A14D-2DE4FEFAD3A6@kdbarto.org>

As a university student in the 1980s we had a cluster of Sun 3/50s using 
a Gould computer as a file server over NFS.  The system administrators 
had quotas enabled (5MB per student) to prevent students gobbling up 
disk space.

Here's an email I received when I used more disk space than what was 
allowed.

> From: Tim [...] <[...]@doc.ic.ac.uk>
> Date: Tue, 13 Feb 90 10:54:18 GMT
> X-Mailer: Mail User's Shell (7.0.3 12/22/89)
> To: zmact61@doc.ic.ac.uk
> Subject: quota
> Message-ID:  <9002131054.aa20550@tgould.doc.ic.ac.uk>
> Status: ORr
> 
> D Spinellis
> 
> I see you have taken advantage of a small admin. oversight when
> no quotas were set for your class.
> 
> On Friday 16th I shall be setting your disk quota to 5Mb, and your 
> inode quota to 500.   Please take appropriate action.
> 
> Disk quotas for (no account) (uid 1461):
> Filesystem     usage  quota  limit    timeleft  files  quota  limit    timeleft
> /home/gould/teach
>                18545  20000  21000               1602   1700   1750            
> /home/gould/staff
>                    0    200    250                  0     40     50      


Diomidis

On 30-May-19 16: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
> 
> 

  reply	other threads:[~2019-05-30 14:30 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 [this message]
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
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=f7d3a1e3-488b-6abf-a041-ad682b82bb16@aueb.gr \
    --to=dds@aueb.gr \
    --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).