[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20111108004615.39477beb@lxorguk.ukuu.org.uk>
Date: Tue, 8 Nov 2011 00:46:15 +0000
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Lennart Poettering <mzxreary@...inter.de>
Cc: Kay Sievers <kay.sievers@...y.org>, Davidlohr Bueso <dave@....org>,
Christoph Hellwig <hch@...radead.org>,
Hugh Dickins <hughd@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
lkml <linux-kernel@...r.kernel.org>, linux-mm@...ck.org
Subject: Re: [RFC PATCH] tmpfs: support user quotas
> And half of the other resource limits are "oddities" too?
> For example RLIMIT_SIGPENDING is per-user and so is RLIMIT_MSGQUEUE,
> and others too.
When you look at the standards - yes.
> > And the standards have no idea how a resource limit hit for an fs would
> > be reported, nor how an app installer would check for it. Quota on the
> > other hand is defined behaviour.
>
> EDQUOT is POSIX, but afaik there is no POSIX standardized API for quota,
> is there? i.e. the reporting of the user hitting quota is defined, but
Its part of Unix and its well defined and used by applications, both for
hitting quota (the easy bit), checking quota (when checking space for
things particularly), and manipulating them
The latter bit is nice, it means you can mount with a user quota set in
the mount options, and if you want then use quota tools to change the
quota of a specific user or two that have special rules.
Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists