All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Hudec <bulb@ucw.cz>
To: Chris Wedgwood <cw@f00f.org>
Cc: Jan Hudec <bulb@ucw.cz>,
	"Stefan (metze) Metzmacher" <metze@metzemix.de>,
	"Stephen C. Tweedie" <sct@redhat.com>,
	viro@math.psu.edu, linux-fsdevel@vger.kernel.org,
	akpm@zip.com.au, Andreas Dilger <adilger@clusterfs.com>,
	ext2-devel@lists.sourceforge.net,
	jfs-discussion@www-124.southbury.usf.ibm.com,
	linux-xfs@oss.sgi.com,
	Alexander Bokovoy <a.bokovoy@sam-solutions.net>
Subject: Re: default quota limits in linux (via quotactl())
Date: Tue, 28 Jan 2003 10:46:19 +0100	[thread overview]
Message-ID: <20030128094619.GO28513@vagabond> (raw)
In-Reply-To: <20030128094014.GA23257@f00f.org>

On Tue, Jan 28, 2003 at 01:40:14AM -0800, Chris Wedgwood wrote:
> On Tue, Jan 28, 2003 at 10:32:50AM +0100, Jan Hudec wrote:
> 
> > It still isn't a kernel problem, but a user-space one. You need to
> > get or write a PAM module, that will check wether quotas are set for
> > user being authenticated and if not, set them. You could even store
> > the qutoas in the LDAP (or some other) database and check them when
> > a user logs in...
> 
> consider 1 million users where only a small percentage of them will
> ever write to the fs ... why even store 1 million quota values
> needlessly at all?

While all the 1 milion users actualy ever LOG IN that site?

And... do they ever log into that site AT THE SAME MOMENT?

> surely the argument for a default here isn't a terrible one?

-------------------------------------------------------------------------------
						 Jan 'Bulb' Hudec <bulb@ucw.cz>

  parent reply	other threads:[~2003-01-28  9:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-27 14:41 default quota limits in linux (via quotactl()) Stefan (metze) Metzmacher
2003-01-27 16:22 ` Stephen C. Tweedie
2003-01-28  6:43   ` Stefan (metze) Metzmacher
2003-01-28  6:54   ` Stefan (metze) Metzmacher
2003-01-28  9:32     ` Jan Hudec
     [not found]       ` <20030128094014.GA23257@f00f.org>
2003-01-28  9:46         ` Jan Hudec [this message]
     [not found]           ` <20030128101310.GA23320@f00f.org>
2003-01-28 10:57             ` Jan Hudec
     [not found]               ` <20030128112034.GA23731@f00f.org>
2003-01-28 12:37                 ` Jan Hudec
2003-01-28 13:32                   ` Stefan (metze) Metzmacher
2003-01-28 15:18                     ` Walt H
2003-01-28 15:27                       ` Stefan Metzmacher
2003-01-29 16:34                     ` Juan Quintela

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=20030128094619.GO28513@vagabond \
    --to=bulb@ucw.cz \
    --cc=a.bokovoy@sam-solutions.net \
    --cc=adilger@clusterfs.com \
    --cc=akpm@zip.com.au \
    --cc=cw@f00f.org \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=jfs-discussion@www-124.southbury.usf.ibm.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@oss.sgi.com \
    --cc=metze@metzemix.de \
    --cc=sct@redhat.com \
    --cc=viro@math.psu.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.