All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Chris Murphy <lists@colorremedies.com>,
	Stan Hoeppner <stan@hardwarefreak.com>,
	xfs@oss.sgi.com
Subject: Re: Enforcing quota for root user
Date: Wed, 12 Nov 2014 10:34:19 +1100	[thread overview]
Message-ID: <20141111233419.GX28565@dastard> (raw)
In-Reply-To: <54628F7B.7080604@sandeen.net>

On Tue, Nov 11, 2014 at 04:36:43PM -0600, Eric Sandeen wrote:
> On 11/11/14 4:32 PM, Dave Chinner wrote:
> > On Tue, Nov 11, 2014 at 11:00:25AM -0700, Chris Murphy wrote:
> >>
> >> On Nov 11, 2014, at 8:36 AM, Stan Hoeppner <stan@hardwarefreak.com> wrote:
> >>
> >>> On 11/11/2014 04:22 AM, Cyril Scetbon wrote:
> >>>> That's what I've read first, but someone showed me a sample where it works. He just told me he was using project quota. However, does it make sense ? 
> >>>> I've also read somewhere else that quota is never enforced for root user (id,gid=0) that's why I was testing it ....
> >>>
> >>> No, it doesn't make sense.  Why would you want to enforce quotas for root?
> >>
> >> A week ago I tried this and project quotas appear to apply to root.
> > 
> > By intent and design. Project quotas are not a user/group based
> > quota and so there is no exemption for any user.
> 
> However, at least according to the manpage, "project ID 0" is not
> enforced.  Granted, that is not a *user* exception.

Correct, and again by intent and design as project quotas are
optional.  i.e. there has to be some way of ensuring non-project ID
controlled files won't have quota enforcement applied to them. ;)

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2014-11-11 23:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-10 22:46 Enforcing quota for root user Cyril Scetbon
2014-11-11  6:56 ` Stan Hoeppner
2014-11-11 10:22   ` Cyril Scetbon
2014-11-11 15:36     ` Stan Hoeppner
2014-11-11 18:00       ` Chris Murphy
2014-11-11 22:32         ` Dave Chinner
2014-11-11 22:36           ` Eric Sandeen
2014-11-11 23:34             ` Dave Chinner [this message]
2014-11-11 23:35           ` Chris Murphy
2014-11-12  0:09             ` Dave Chinner
2014-11-12 13:55       ` Cyril Scetbon

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=20141111233419.GX28565@dastard \
    --to=david@fromorbit.com \
    --cc=lists@colorremedies.com \
    --cc=sandeen@sandeen.net \
    --cc=stan@hardwarefreak.com \
    --cc=xfs@oss.sgi.com \
    /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.