The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Andreas Kusalananda Kähäri" <andreas.kahari@abc.se>
To: David <david@kdbarto.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Quotas - did anyone ever use them?
Date: Thu, 30 May 2019 16:55:10 +0200	[thread overview]
Message-ID: <20190530145510.GA58792@eeyore.my.domain> (raw)
In-Reply-To: <975B93B6-AD7C-41B5-A14D-2DE4FEFAD3A6@kdbarto.org>

On Thu, May 30, 2019 at 06:49:05AM -0700, 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

At my current workplace, we use quotas on shared systems (Linux
compute clusters and multi-user interactive login nodes).  When I was
at univeristy (early 1990's), the SunOS and Solaris systems at the
department had the home directories mounted over NFS, and there were
quotas in effect on the file server.

On VM systems that I set up privately, where /home is not on a separate
partition, I use quotas for my own account (because sometimes I want to
use a really tiny disk, and limiting the size of /home is easier with
quotas than through partitioning off the correct size on the first try).

I have access to a shared non-work related OpenBSD and Linux system
which does *not* use quotas, and it makes me slightly nervous because
I don't actually know how much disk space I'm *allowed* to use without
being told off by a human operator.  It would have been better if they
had had quotas enabled and then made it easy to ask for more space
thourgh a simple email to the admins.

-- 
Kusalananda
Sweden

  parent reply	other threads:[~2019-05-30 15:02 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 [this message]
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=20190530145510.GA58792@eeyore.my.domain \
    --to=andreas.kahari@abc.se \
    --cc=david@kdbarto.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).