From: Jan Hudec <bulb@ucw.cz>
To: "Stefan (metze) Metzmacher" <metze@metzemix.de>
Cc: "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:32:50 +0100 [thread overview]
Message-ID: <20030128093250.GM28513@vagabond> (raw)
In-Reply-To: <5.2.0.9.2.20030128074810.0218c4f8@post.webmailer.de>
On Tue, Jan 28, 2003 at 07:54:08AM +0100, Stefan (metze) Metzmacher wrote:
> At 16:22 27.01.2003 +0000, Stephen C. Tweedie wrote:
> >That's a user-space problem. A new user typically won't have a writable
> >area within /home until the sysadmin has created the new home directory,
> >so it's really up to the sysadmin to make sure that the quota for the
> >home filesystem has been set at the same time.
>
> What is if we have 500.000 users and 300.000 group in LDAP
>
> and set up a new server, witch is intended to store data from ~1000 users
> 500 group
>
> should the admin really run setquota ... for each of the 500.000 users and
> 300.000 group
>
> that's are 800.000 quota entries in the filesystem and only 1500 are really
> used
>
> ans this entries cost disk space too, so if we have two default entries
> (one for users and one for groups) then only every user witch really uses
> this filesystem would get a quota entry when he starts to own diskspace on
> this filesystem and we would have only 1502 quota entries stored on disk!
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...
-------------------------------------------------------------------------------
Jan 'Bulb' Hudec <bulb@ucw.cz>
next prev parent reply other threads:[~2003-01-28 9:32 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 [this message]
[not found] ` <20030128094014.GA23257@f00f.org>
2003-01-28 9:46 ` Jan Hudec
[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=20030128093250.GM28513@vagabond \
--to=bulb@ucw.cz \
--cc=a.bokovoy@sam-solutions.net \
--cc=adilger@clusterfs.com \
--cc=akpm@zip.com.au \
--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.