From: Herbert Poetzl (herbert_at_13thfloor.at)
Date: Fri 12 Sep 2003 - 14:32:45 BST
On Fri, Sep 12, 2003 at 07:50:41AM +0300, Alex Lyashkov wrote:
> On Friday 12 September 2003 02:44, Stephan Sachse wrote:
> > On Thu, Sep 11, 2003 at 07:11:44PM +0200, Herbert Poetzl wrote:
> > > > - - - - - - - - - - - - - - - >8 - - - - - - - - - - - - - - -
> > > > [root_at_v01 /]# quotaon -vgu /dev/hdv1
> > > > quotaon: using //aquota.group on /dev/hdv1 [/]: Die Operation ist nicht
> > > > erlaubt
> > > > quotaon: using //aquota.user on /dev/hdv1 [/]: Die Operation ist nicht
> > > > erlaubt
> > > > - - - - - - - - - - - - - - - 8< - - - - - - - - - - - - - - -
> > > >
> > > > "quotacheck -avgu" works fine
> > >
> > > hmm, usually quotacheck -avgu doesn't work, because it
> > > complains that the filesystem is mounted, bla bla ...
> > > so normally quotacheck -vaugm is used to override
> >
> > ups sorry.
> > i do "quotacheck -avgum" not "-avgu" ;)
> >
> > > this leaves me with two causes for your failure:
> > >
> > > - you did not specify CAP_SYS_ADMIN in the vserver
> > > config file (most likely)
> > >
> > > - your quotatools are somewhat different from the
> > > 'normal' quota-tools-3.09 (at least 3.04 is required)
> >
> > CAP_SYS_ADMIN is set in vserver config file and quota-tools-3.09 are
> ^^^^^^^^^^^^^^^^^^^^
> > installed.
> hmmm.. Herbert it`s CAP need for you new diskquotas ?
it is needed from the 'unpatched' kernel, and I do
not change this behaviour yet, we should talk about extending
the capabilites, best by adding a separate capability list
per context, this would allow a finer grained control over
system capabilities per vserver ...
what do you think about it?
best,
Herbert
> --
> With best regards,
> Alex