From: Herbert Poetzl (herbert_at_13thfloor.at)
Date: Tue 21 Sep 2004 - 14:37:32 BST
On Tue, Sep 21, 2004 at 08:36:50AM -0400, Marc E. Fiuczynski wrote:
> Here are the compile errors...
>
> [mef_at_localhost vdlimit-0.01]$ make
> cc -g -Wall -O2 -Ivserver -o vdlimit vdlimit.c
> In file included from vdlimit.c:23:
> vserver.h:8: error: syntax error before "vserver"
> vserver.h:8: warning: type defaults to `int' in declaration of `_syscall3'
> vdlimit.c: In function `main':
> vdlimit.c:114: warning: implicit declaration of function `vserver'
> vdlimit.c: At top level:
> vserver.h:8: warning: `_syscall3' declared `static' but never defined
> make: *** [vdlimit] Error 1
>
> Easy to work around by ifdef ou the _syscall3 in vserver.h. But then I
> get...
yep, right. just curious, debian?
> [mef_at_localhost vdlimit-0.01]$ make
> cc -g -Wall -O2 -Ivserver -o vdlimit vdlimit.c
> vdlimit.c: In function `main':
> vdlimit.c:114: warning: implicit declaration of function `vserver'
> /tmp/cc3JmY03.o(.text+0x1ac): In function `main':
> /home/mef/projects/vdlimit-0.01/vdlimit.c:159: undefined reference to
> `vserver'
> /tmp/cc3JmY03.o(.text+0x24f):/home/mef/projects/vdlimit-0.01/vdlimit.c:150:
> undefined reference to `vserver'
> /tmp/cc3JmY03.o(.text+0x28e):/home/mef/projects/vdlimit-0.01/vdlimit.c:135:
> undefined reference to `vserver'
> /tmp/cc3JmY03.o(.text+0x2c3):/home/mef/projects/vdlimit-0.01/vdlimit.c:130:
> undefined reference to `vserver'
> /tmp/cc3JmY03.o(.text+0x2ef):/home/mef/projects/vdlimit-0.01/vdlimit.c:114:
> undefined reference to `vserver'
> collect2: ld returned 1 exit stat
>
> Probably easy to work around, but I figured the right thing to do was
> integrate with util-vserver.
totally agreed, the vdlimit tool (as all the
experimental tools) are just for testing, enrico
usually does the 'real' work for the userspace
tools ...
thanks to Enrico for that!
best,
Herbert
> Marc
>
> -----Original Message-----
> From: Herbert Poetzl [mailto:herbert_at_13thfloor.at]
> Sent: Tuesday, September 21, 2004 8:20 AM
> To: Marc E. Fiuczynski
> Cc: vserver_at_list.linux-vserver.org
> Subject: Re: [Vserver] vdlimit
>
>
> On Tue, Sep 21, 2004 at 07:24:22AM -0400, Marc E. Fiuczynski wrote:
> > It works flawlessly, of course. My mistake was to give it a dev (as
> > necessary for cq-tools) rather than a file in the fs as an argument.
>
> so you created a dlimit entry for the filesystem the
> device is on ... understandable ...
>
> > Will import the util-vserver 0.30.193 code, merge the vdlimit.c file, and
> > then send the diff to the mailing list (or just Enrico and you).
>
> yeah, a 'solid' util-vserver (alpha) implementation
> would be nice, but double-check with enrico, if that
> isn't already work in progress ...
>
> still I'm interested in the compile errors you got
> with the vdlimit experimental tool ..
>
> TIA,
> Herbert
>
> > Cheers,
> > Marc
> >
> > -----Original Message-----
> > From: Herbert Poetzl [mailto:herbert_at_13thfloor.at]
> > Sent: Tuesday, September 21, 2004 3:07 AM
> > To: Marc E. Fiuczynski
> > Cc: vserver_at_list.linux-vserver.org
> > Subject: Re: [Vserver] vdlimit
> >
> >
> > On Mon, Sep 20, 2004 at 09:09:03PM -0400, Marc E. Fiuczynski wrote:
> > > Hi,
> > >
> > > Was trying to get vdlimit to work. First, i grabbed the vdlimit 0.01 tar
> > > ball from the Experimental area. Is that what I should grab?
> >
> > hmm, yes for 1.9.x ...
> >
> > > Any way, tried compiling it without much luck.
> >
> > interesting, any trace of the compile errors ...
> >
> > > Took the vdlimit.c file and integrated it with util-vserver 0.30.
> >
> > hmm, well, okay ... so be it ...
> >
> > > After some fiddling I got that compiled. It seems to
> > > work on a 2.6.8.1 system with vserver 1.9.2---i.e., the
> > > get_dlimit call appears to read back the value that I set.
> >
> > > However, when I enter the vserver and do a df, I don't
> > > see the disklimit value that I set. What am I getting
> > > wrong here?
> >
> > assumed that it really does work, you have tagxid
> > enabled for the filesystem, the dlimit entry was
> > added, and the limit set, then the df/df -i should
> > adjust the values to 'match' the limits, i.e. it
> > will reduce the available size to the minimum of
> > available space and configured limit ...
> >
> > remember, values are
> > blocks/max-blocks/inodes/max-inodes/root-reserve
> > and don't forget to specify a path to the filesystem
> >
> > example:
> >
> > # mount -o tagxid /dev/discs/disc1/part1 /vservers
> > # chcontext --ctx 100 df
> > New security context is 100
> > Filesystem 1K-blocks Used Available Use% Mounted on
> > /dev/root 31698 25243 6455 80% /
> > /dev/discs/disc1/part1 253775 185884 54789 78% /vservers
> >
> > # vdlimit -a -x 100 -S 0,1000,0,100,10 /vservers
> > # chcontext --ctx 100 df
> > New security context is 100
> > Filesystem 1K-blocks Used Available Use% Mounted on
> > /dev/root 31698 25243 6455 80% /
> > /dev/discs/disc1/part1 1000 0 899 0% /vservers
> >
> > (vdlimit compiled on mandrake, then tested on
> > 2.6.9-rc2-vs1.9.2.28.4 but should work since
> > 1.9.2, even for some 1.9.1.x versions)
> >
> > HTH,
> > Herbert
> >
> > > Marc
> > >
> > >
> > >
> > > _______________________________________________
> > > Vserver mailing list
> > > Vserver_at_list.linux-vserver.org
> > > http://list.linux-vserver.org/mailman/listinfo/vserver
>
> _______________________________________________
> Vserver mailing list
> Vserver_at_list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
_______________________________________________
Vserver mailing list
Vserver_at_list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver