From: Noèl Köthe (noel_at_debian.org)
Date: Sun 28 Dec 2003 - 14:09:54 GMT
Hello,
I'm runing a production machine with 2.4.23-vs1.00 and vserver 0.23.
The settings are:
S_HOSTNAME="v62"
S_CONTEXT="62"
IPROOT="192.168.0.62"
...
and this results in the context id 62:
CTX PROC VSZ RSS userTIME sysTIME UPTIME NAME DESCRIPTION
0 36 100MB 5kB 12m00.44 12m39.91 25d05h16 root server
62 76 1GB 295kB 1h44m54 12m42.17 25d05h15 v62
^^
Now runing trying v1.20 (had it also on 1.22 and my test with 1.3.1) on
2.4.23 (on a testing machine) with 0.29 results in:
S_HOSTNAME="v101"
S_CONTEXT="101"
IPROOT="192.168.74.101"
...
CTX PROC VSZ RSS userTIME sysTIME UPTIME NAME DESCRIPTION
0 28 38MB 4kB m05.38 m05.45 2m12.15 root server
49152 7 15MB 1kB m00.05 m00.03 1m29.09 v101
Because vserver.conf(5) doesn't list S_CONTEXT (anymore?) it looks like
its removed. Right?
(I checked http://www.solucorp.qc.ca/changes.hc?projet=vserver but
couldn't find a note about this option between 0.23 and 0.29)
The question for me is now does v101 will always have 49152?
I want to use context limit and want to do set the limit on a vserver
but the script don't know the CTX value for "cqdlim". With the S_CONTEXT
I could justed the last octed of the IP.
Why was S_CONTEXT removed?
Any idea how I could use "cqlim" in a script when setting up a new
vserver when I dont know the CTX ID?
thank you.
-- Noèl Köthe <noel debian.org> Debian GNU/Linux, www.debian.org
_______________________________________________ Vserver mailing list Vserver_at_list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver