http://linux-vserver.org/api.php?action=feedcontributions&user=UdoBurghardt&feedformat=atomLinux-VServer - User contributions [en]2024-03-29T07:11:48ZUser contributionsMediaWiki 1.20.2http://linux-vserver.org/User:UdoBurghardtUser:UdoBurghardt2006-10-16T12:35:20Z<p>UdoBurghardt: </p>
<hr />
<div>{| width="99%"<br />
|<br />
Stumbling over linux-vserver two or three years ago I currently use it on an Athlon X2 running debian Gnu/Linux. Just for fun (it is a private machine, not really a "productive system") this server runs 11 vserver instances continously. I've never had to blame vserver responsible for a malfunction. Thank you!<br />
<br />
=== Profession ===<br />
For four years now I earn my money by being a System Administrator at the [http://www.ifi.informatik.uni-goettingen.de Institute for Informatics] (Germany/Göttingen). Most virtual machines are running on vmware's GSX product. But linux-vserver is being evaluated and may be used for some of them in the future...<br />
<br />
|align="right" valign="top"| <br />
<br />
|}<br />
----<br />
Udo Burghardt, http://udoburghardt.de, Linux User [http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=139174 #139174]</div>UdoBurghardthttp://linux-vserver.org/ProcFSProcFS2006-10-16T12:05:20Z<p>UdoBurghardt: </p>
<hr />
<div>Information abaut the current runtime conditions can be found inside the /proc directory. The very most information is read-only. Because it usually is world-readable you do not have to gain root access to look at this information. <br />
<br />
== Per Host ==<br />
Regarding the host system there is only one single file present:<br />
<br />
=== info ===<br />
/proc/virtual/info<br />
VCIVersion: 0002:0002<br />
VCISyscall: 236<br />
VCIKernel: 03000016<br />
<br />
You may compare this info to the output of "vserver-info"; you will recognize two of those entries under a slightly different name while VCIKernel seems to be missing:<br />
<br />
x2:~# vserver-info<br />
Versions:<br />
Kernel: 2.6.17-2-vserver-amd64<br />
VS-API: 0x00020002<br />
util-vserver: 0.30.210; Sep 30 2006, 23:55:41<br />
Features:<br />
CC: gcc, gcc (GCC) 4.1.2 20060928 (prerelease) (Debian 4.1.1-15)<br />
CXX: g++, g++ (GCC) 4.1.2 20060928 (prerelease) (Debian 4.1.1-15)<br />
CPPFLAGS: ''<br />
CFLAGS: '-Wall -g -O2 -std=c99 -Wall -pedantic -W -funit-at-a-time'<br />
CXXFLAGS: '-g -O2 -ansi -Wall -pedantic -W -fmessage-length=0 -funit-at-a-time'<br />
build/host: x86_64-pc-linux-gnu/x86_64-pc-linux-gnu<br />
Use dietlibc: yes<br />
Build C++ programs: yes<br />
Build C99 programs: yes<br />
Available APIs: compat,v11,fscompat,v13,net,oldproc,olduts<br />
ext2fs Source: e2fsprogs<br />
syscall(2) invocation: alternative<br />
vserver(2) syscall#: 236/glibc<br />
<br />
== Per vserver instance ==<br />
<br />
=== info ===<br />
This shows the context id, vx_info location and init pid<br />
<br />
/proc/virtual/<id>/info <br />
ID: 1001<br />
Info: 83c37000<br />
Init: 0<br />
<br />
=== status ===<br />
This contains the usage count (references) and task count, as well as the context flags, capability boundary and context capabilities<br />
<br />
/proc/virtual/<id>/status <br />
UseCnt: 38<br />
Tasks: 16<br />
Flags: 0000000000000000<br />
BCaps: 00000000d46c04ff<br />
CCaps: 0000000000000000<br />
Ticks: 0<br />
<br />
=== sched ===<br />
Shows the current amount of tokens, scheduler parameters (fill rate, interval, min/max), the priority bias and the calculated vavavoom (priority bonus)<br />
<br />
/proc/virtual/<id>/sched <br />
Token: 0<br />
FillRate: 1<br />
Interval: 4<br />
TokensMin: 6<br />
TokensMax: 50<br />
PrioBias: 0<br />
VaVaVoom: 0<br />
cpu 0: 0 0 0<br />
<br />
=== cacct ===<br />
This one accounts socket messages for the listed protocols, as incoming messages/bytes and outgoing messages/bytes<br />
<br />
/proc/virtual/<id>/cacct <br />
UNSPEC: 0/0 0/0 0/0 <br />
UNIX: 35/2375 35/2375 0/0 <br />
INET: 12/531 56/1937 57/1705 <br />
INET6: 0/0 0/0 0/0 <br />
OTHER: 0/0 0/0 0/0 <br />
forks: 0<br />
<br />
=== cvirt ===<br />
This contains the uptime bias, utsname settings (sys, node, rel, vers, machine, domain), the number of threads, thread stats (running, uninterruptible, on hold), the number of load updates, the load averages (1,5,15) and the number of forks<br />
<br />
/proc/virtual/<id>/cvirt <br />
BiasUptime: 49.73<br />
SysName: Linux<br />
NodeName: XXXX.test.org<br />
Release: 2.6.11-rc5<br />
Version: #12 Sun Feb 27 01:07:29 CET 2005<br />
Machine: i686<br />
DomainName: <br />
nr_threads: 16<br />
nr_running: 0<br />
nr_unintr: 0<br />
nr_onhold: 0<br />
load_updates: 14585<br />
loadavg: 0.00 0.00 0.00<br />
total_forks: 272<br />
<br />
=== limit ===<br />
Limit columns are: current (1), max observed (2), limit (3) and number of hits (4) <br />
<br />
Limit rows are: processes, virtual memory, locked memory, resident set size, anonymous memory, number of files, filedescriptors, locks, sockets, message queues, and shared memory<br />
<br />
/proc/virtual/<id>/limit <br />
PROC: 16 17 -1 0<br />
VM: 14440 15331 -1 0<br />
VML: 0 0 -1 0<br />
RSS: 5478 5847 -1 0<br />
ANON: 1516 1516 -1 0<br />
FILES: 140 155 -1 0<br />
OFD: 122 122 -1 0<br />
LOCKS: 1 3 -1 0<br />
SOCK: 9 9 -1 0<br />
MSGQ: 0 0 -1 0<br />
SHM: 0 0 -1 0<br />
<br />
== Debugging Control ==<br />
This complete directory seems not to be present by default. Possibly there is a compile- or a runtime-switch to enable debugging.<br />
<br />
/proc/sys/vserver<br />
.../debug_switch<br />
.../debug_xid<br />
.../debug_cvirt<br />
.../debug_limit<br />
.../debug_dlim<br />
.../debug_nid<br />
.../debug_net<br />
/proc/sys/vserver/debug_switch<br />
/proc/sys/vserver/debug_xid<br />
/proc/sys/vserver/debug_cvirt<br />
/proc/sys/vserver/debug_limit<br />
/proc/sys/vserver/debug_dlim<br />
/proc/sys/vserver/debug_nid<br />
/proc/sys/vserver/debug_net<br />
<br />
If the directory exist you should be able to create these files by issuing commands like:<br />
<br />
echo 255 >/proc/sys/vserver/debug_switch<br />
<br />
The bigger problem is to find out which values are useful, see [[Debugging]] for details.<br />
<br />
----<br />
''Please note: some samples are simply copied from the old wiki at http://oldwiki.linux-vserver.org/HowTo+Read+ProcFS, some other are captured from an Athlon AMD X2 system. They do not necessarily fit together.''</div>UdoBurghardthttp://linux-vserver.org/ProcFSProcFS2006-10-16T12:04:26Z<p>UdoBurghardt: </p>
<hr />
<div>Information abaut the current runtime conditions can be found inside the /proc directory. The very most information is read-only. Because it usually is world-readable you do not have to gain root access to look at this information. <br />
<br />
== Per Host ==<br />
Regarding the host system there is only one file present:<br />
<br />
=== info ===<br />
<br />
/proc/virtual/info<br />
VCIVersion: 0002:0002<br />
VCISyscall: 236<br />
VCIKernel: 03000016<br />
<br />
You may compare this info to the output of "vserver-info"; you will recognize two of those entries under a slightly different name while VCIKernel seems to be missing:<br />
<br />
x2:~# vserver-info<br />
Versions:<br />
Kernel: 2.6.17-2-vserver-amd64<br />
VS-API: 0x00020002<br />
util-vserver: 0.30.210; Sep 30 2006, 23:55:41<br />
Features:<br />
CC: gcc, gcc (GCC) 4.1.2 20060928 (prerelease) (Debian 4.1.1-15)<br />
CXX: g++, g++ (GCC) 4.1.2 20060928 (prerelease) (Debian 4.1.1-15)<br />
CPPFLAGS: ''<br />
CFLAGS: '-Wall -g -O2 -std=c99 -Wall -pedantic -W -funit-at-a-time'<br />
CXXFLAGS: '-g -O2 -ansi -Wall -pedantic -W -fmessage-length=0 -funit-at-a-time'<br />
build/host: x86_64-pc-linux-gnu/x86_64-pc-linux-gnu<br />
Use dietlibc: yes<br />
Build C++ programs: yes<br />
Build C99 programs: yes<br />
Available APIs: compat,v11,fscompat,v13,net,oldproc,olduts<br />
ext2fs Source: e2fsprogs<br />
syscall(2) invocation: alternative<br />
vserver(2) syscall#: 236/glibc<br />
<br />
== Per vserver instance ==<br />
<br />
=== info ===<br />
This shows the context id, vx_info location and init pid<br />
<br />
/proc/virtual/<id>/info <br />
ID: 1001<br />
Info: 83c37000<br />
Init: 0<br />
<br />
=== status ===<br />
This contains the usage count (references) and task count, as well as the context flags, capability boundary and context capabilities<br />
<br />
/proc/virtual/<id>/status <br />
UseCnt: 38<br />
Tasks: 16<br />
Flags: 0000000000000000<br />
BCaps: 00000000d46c04ff<br />
CCaps: 0000000000000000<br />
Ticks: 0<br />
<br />
=== sched ===<br />
Shows the current amount of tokens, scheduler parameters (fill rate, interval, min/max), the priority bias and the calculated vavavoom (priority bonus)<br />
<br />
/proc/virtual/<id>/sched <br />
Token: 0<br />
FillRate: 1<br />
Interval: 4<br />
TokensMin: 6<br />
TokensMax: 50<br />
PrioBias: 0<br />
VaVaVoom: 0<br />
cpu 0: 0 0 0<br />
<br />
=== cacct ===<br />
This one accounts socket messages for the listed protocols, as incoming messages/bytes and outgoing messages/bytes<br />
<br />
/proc/virtual/<id>/cacct <br />
UNSPEC: 0/0 0/0 0/0 <br />
UNIX: 35/2375 35/2375 0/0 <br />
INET: 12/531 56/1937 57/1705 <br />
INET6: 0/0 0/0 0/0 <br />
OTHER: 0/0 0/0 0/0 <br />
forks: 0<br />
<br />
=== cvirt ===<br />
This contains the uptime bias, utsname settings (sys, node, rel, vers, machine, domain), the number of threads, thread stats (running, uninterruptible, on hold), the number of load updates, the load averages (1,5,15) and the number of forks<br />
<br />
/proc/virtual/<id>/cvirt <br />
BiasUptime: 49.73<br />
SysName: Linux<br />
NodeName: XXXX.test.org<br />
Release: 2.6.11-rc5<br />
Version: #12 Sun Feb 27 01:07:29 CET 2005<br />
Machine: i686<br />
DomainName: <br />
nr_threads: 16<br />
nr_running: 0<br />
nr_unintr: 0<br />
nr_onhold: 0<br />
load_updates: 14585<br />
loadavg: 0.00 0.00 0.00<br />
total_forks: 272<br />
<br />
=== limit ===<br />
Limit columns are: current (1), max observed (2), limit (3) and number of hits (4) <br />
<br />
Limit rows are: processes, virtual memory, locked memory, resident set size, anonymous memory, number of files, filedescriptors, locks, sockets, message queues, and shared memory<br />
<br />
/proc/virtual/<id>/limit <br />
PROC: 16 17 -1 0<br />
VM: 14440 15331 -1 0<br />
VML: 0 0 -1 0<br />
RSS: 5478 5847 -1 0<br />
ANON: 1516 1516 -1 0<br />
FILES: 140 155 -1 0<br />
OFD: 122 122 -1 0<br />
LOCKS: 1 3 -1 0<br />
SOCK: 9 9 -1 0<br />
MSGQ: 0 0 -1 0<br />
SHM: 0 0 -1 0<br />
<br />
== Debugging Control ==<br />
This complete directory seems not to be present by default. Possibly there is a compile- or a runtime-switch to enable debugging.<br />
<br />
/proc/sys/vserver<br />
.../debug_switch<br />
.../debug_xid<br />
.../debug_cvirt<br />
.../debug_limit<br />
.../debug_dlim<br />
.../debug_nid<br />
.../debug_net<br />
/proc/sys/vserver/debug_switch<br />
/proc/sys/vserver/debug_xid<br />
/proc/sys/vserver/debug_cvirt<br />
/proc/sys/vserver/debug_limit<br />
/proc/sys/vserver/debug_dlim<br />
/proc/sys/vserver/debug_nid<br />
/proc/sys/vserver/debug_net<br />
<br />
If the directory exist you should be able to create these files by issuing commands like:<br />
<br />
echo 255 >/proc/sys/vserver/debug_switch<br />
<br />
The bigger problem is to find out which values are useful, see [[Debugging]] for details.<br />
<br />
----<br />
''Please note: some samples are simply copied from the old wiki at http://oldwiki.linux-vserver.org/HowTo+Read+ProcFS, some other are captured from an Athlon AMD X2 system. They do not necessarily fit together.''</div>UdoBurghardthttp://linux-vserver.org/ProcFSProcFS2006-10-16T12:03:37Z<p>UdoBurghardt: </p>
<hr />
<div>Information abaut the current runtime conditions can be found inside the /proc directory. The very most information is read-only. Because it usually is world-readable you do not have to gain root access to look at this information. Files explained on this page are:<br />
<br />
/proc/virtual<br />
.../info<br />
<br />
/proc/virtual/<id><br />
.../info<br />
.../status<br />
.../sched<br />
.../cvirt<br />
.../cacct<br />
.../limit<br />
<br />
== Per Host ==<br />
Regarding the host system there is only one file present:<br />
<br />
=== info ===<br />
<br />
/proc/virtual/info<br />
VCIVersion: 0002:0002<br />
VCISyscall: 236<br />
VCIKernel: 03000016<br />
<br />
You may compare this info to the output of "vserver-info"; you will recognize two of those entries under a slightly different name while VCIKernel seems to be missing:<br />
<br />
x2:~# vserver-info<br />
Versions:<br />
Kernel: 2.6.17-2-vserver-amd64<br />
VS-API: 0x00020002<br />
util-vserver: 0.30.210; Sep 30 2006, 23:55:41<br />
Features:<br />
CC: gcc, gcc (GCC) 4.1.2 20060928 (prerelease) (Debian 4.1.1-15)<br />
CXX: g++, g++ (GCC) 4.1.2 20060928 (prerelease) (Debian 4.1.1-15)<br />
CPPFLAGS: ''<br />
CFLAGS: '-Wall -g -O2 -std=c99 -Wall -pedantic -W -funit-at-a-time'<br />
CXXFLAGS: '-g -O2 -ansi -Wall -pedantic -W -fmessage-length=0 -funit-at-a-time'<br />
build/host: x86_64-pc-linux-gnu/x86_64-pc-linux-gnu<br />
Use dietlibc: yes<br />
Build C++ programs: yes<br />
Build C99 programs: yes<br />
Available APIs: compat,v11,fscompat,v13,net,oldproc,olduts<br />
ext2fs Source: e2fsprogs<br />
syscall(2) invocation: alternative<br />
vserver(2) syscall#: 236/glibc<br />
<br />
== Per vserver instance ==<br />
<br />
=== info ===<br />
This shows the context id, vx_info location and init pid<br />
<br />
/proc/virtual/<id>/info <br />
ID: 1001<br />
Info: 83c37000<br />
Init: 0<br />
<br />
=== status ===<br />
This contains the usage count (references) and task count, as well as the context flags, capability boundary and context capabilities<br />
<br />
/proc/virtual/<id>/status <br />
UseCnt: 38<br />
Tasks: 16<br />
Flags: 0000000000000000<br />
BCaps: 00000000d46c04ff<br />
CCaps: 0000000000000000<br />
Ticks: 0<br />
<br />
=== sched ===<br />
Shows the current amount of tokens, scheduler parameters (fill rate, interval, min/max), the priority bias and the calculated vavavoom (priority bonus)<br />
<br />
/proc/virtual/<id>/sched <br />
Token: 0<br />
FillRate: 1<br />
Interval: 4<br />
TokensMin: 6<br />
TokensMax: 50<br />
PrioBias: 0<br />
VaVaVoom: 0<br />
cpu 0: 0 0 0<br />
<br />
=== cacct ===<br />
This one accounts socket messages for the listed protocols, as incoming messages/bytes and outgoing messages/bytes<br />
<br />
/proc/virtual/<id>/cacct <br />
UNSPEC: 0/0 0/0 0/0 <br />
UNIX: 35/2375 35/2375 0/0 <br />
INET: 12/531 56/1937 57/1705 <br />
INET6: 0/0 0/0 0/0 <br />
OTHER: 0/0 0/0 0/0 <br />
forks: 0<br />
<br />
=== cvirt ===<br />
This contains the uptime bias, utsname settings (sys, node, rel, vers, machine, domain), the number of threads, thread stats (running, uninterruptible, on hold), the number of load updates, the load averages (1,5,15) and the number of forks<br />
<br />
/proc/virtual/<id>/cvirt <br />
BiasUptime: 49.73<br />
SysName: Linux<br />
NodeName: XXXX.test.org<br />
Release: 2.6.11-rc5<br />
Version: #12 Sun Feb 27 01:07:29 CET 2005<br />
Machine: i686<br />
DomainName: <br />
nr_threads: 16<br />
nr_running: 0<br />
nr_unintr: 0<br />
nr_onhold: 0<br />
load_updates: 14585<br />
loadavg: 0.00 0.00 0.00<br />
total_forks: 272<br />
<br />
=== limit ===<br />
Limit columns are: current (1), max observed (2), limit (3) and number of hits (4) <br />
<br />
Limit rows are: processes, virtual memory, locked memory, resident set size, anonymous memory, number of files, filedescriptors, locks, sockets, message queues, and shared memory<br />
<br />
/proc/virtual/<id>/limit <br />
PROC: 16 17 -1 0<br />
VM: 14440 15331 -1 0<br />
VML: 0 0 -1 0<br />
RSS: 5478 5847 -1 0<br />
ANON: 1516 1516 -1 0<br />
FILES: 140 155 -1 0<br />
OFD: 122 122 -1 0<br />
LOCKS: 1 3 -1 0<br />
SOCK: 9 9 -1 0<br />
MSGQ: 0 0 -1 0<br />
SHM: 0 0 -1 0<br />
<br />
== Debugging Control ==<br />
This complete directory seems not to be present by default. Possibly there is a compile- or a runtime-switch to enable debugging.<br />
<br />
/proc/sys/vserver<br />
.../debug_switch<br />
.../debug_xid<br />
.../debug_cvirt<br />
.../debug_limit<br />
.../debug_dlim<br />
.../debug_nid<br />
.../debug_net<br />
/proc/sys/vserver/debug_switch<br />
/proc/sys/vserver/debug_xid<br />
/proc/sys/vserver/debug_cvirt<br />
/proc/sys/vserver/debug_limit<br />
/proc/sys/vserver/debug_dlim<br />
/proc/sys/vserver/debug_nid<br />
/proc/sys/vserver/debug_net<br />
<br />
If the directory exist you should be able to create these files by issuing commands like:<br />
<br />
echo 255 >/proc/sys/vserver/debug_switch<br />
<br />
The bigger problem is to find out which values are useful, see [[Debugging]] for details.<br />
<br />
----<br />
''Please note: some samples are simply copied from the old wiki at http://oldwiki.linux-vserver.org/HowTo+Read+ProcFS, some other are captured from an Athlon AMD X2 system. They do not necessarily fit together.''</div>UdoBurghardthttp://linux-vserver.org/ProcFSProcFS2006-10-16T12:02:00Z<p>UdoBurghardt: Created mostly with content from old wiki</p>
<hr />
<div>Information abaut the current runtime conditions can be found inside the /proc directory. The very most information is read-only. Because it usually is world-readable you do not have to gain root access to look at this information. <br />
<br />
Files explained on this page:<br />
<br />
/proc/virtual<br />
.../info<br />
<br />
/proc/virtual/<id><br />
.../info<br />
.../status<br />
.../sched<br />
.../cvirt<br />
.../cacct<br />
.../limit<br />
<br />
This directory contains several files which can provide valuable information on the current context state and settings. <br />
<br />
== Per Host ==<br />
Regarding the host system there is only one file present:<br />
<br />
=== info ===<br />
<br />
/proc/virtual/info<br />
VCIVersion: 0002:0002<br />
VCISyscall: 236<br />
VCIKernel: 03000016<br />
<br />
You may compare this info to the output of "vserver-info"; you will recognize two of those entries under a slightly different name while VCIKernel seems to be missing:<br />
<br />
x2:~# vserver-info<br />
Versions:<br />
Kernel: 2.6.17-2-vserver-amd64<br />
VS-API: 0x00020002<br />
util-vserver: 0.30.210; Sep 30 2006, 23:55:41<br />
Features:<br />
CC: gcc, gcc (GCC) 4.1.2 20060928 (prerelease) (Debian 4.1.1-15)<br />
CXX: g++, g++ (GCC) 4.1.2 20060928 (prerelease) (Debian 4.1.1-15)<br />
CPPFLAGS: ''<br />
CFLAGS: '-Wall -g -O2 -std=c99 -Wall -pedantic -W -funit-at-a-time'<br />
CXXFLAGS: '-g -O2 -ansi -Wall -pedantic -W -fmessage-length=0 -funit-at-a-time'<br />
build/host: x86_64-pc-linux-gnu/x86_64-pc-linux-gnu<br />
Use dietlibc: yes<br />
Build C++ programs: yes<br />
Build C99 programs: yes<br />
Available APIs: compat,v11,fscompat,v13,net,oldproc,olduts<br />
ext2fs Source: e2fsprogs<br />
syscall(2) invocation: alternative<br />
vserver(2) syscall#: 236/glibc<br />
<br />
== Per vserver instance ==<br />
<br />
=== info ===<br />
This shows the context id, vx_info location and init pid<br />
<br />
/proc/virtual/<id>/info <br />
ID: 1001<br />
Info: 83c37000<br />
Init: 0<br />
<br />
=== status ===<br />
This contains the usage count (references) and task count, as well as the context flags, capability boundary and context capabilities<br />
<br />
/proc/virtual/<id>/status <br />
UseCnt: 38<br />
Tasks: 16<br />
Flags: 0000000000000000<br />
BCaps: 00000000d46c04ff<br />
CCaps: 0000000000000000<br />
Ticks: 0<br />
<br />
=== sched ===<br />
Shows the current amount of tokens, scheduler parameters (fill rate, interval, min/max), the priority bias and the calculated vavavoom (priority bonus)<br />
<br />
/proc/virtual/<id>/sched <br />
Token: 0<br />
FillRate: 1<br />
Interval: 4<br />
TokensMin: 6<br />
TokensMax: 50<br />
PrioBias: 0<br />
VaVaVoom: 0<br />
cpu 0: 0 0 0<br />
<br />
=== cacct ===<br />
This one accounts socket messages for the listed protocols, as incoming messages/bytes and outgoing messages/bytes<br />
<br />
/proc/virtual/<id>/cacct <br />
UNSPEC: 0/0 0/0 0/0 <br />
UNIX: 35/2375 35/2375 0/0 <br />
INET: 12/531 56/1937 57/1705 <br />
INET6: 0/0 0/0 0/0 <br />
OTHER: 0/0 0/0 0/0 <br />
forks: 0<br />
<br />
=== cvirt ===<br />
This contains the uptime bias, utsname settings (sys, node, rel, vers, machine, domain), the number of threads, thread stats (running, uninterruptible, on hold), the number of load updates, the load averages (1,5,15) and the number of forks<br />
<br />
/proc/virtual/<id>/cvirt <br />
BiasUptime: 49.73<br />
SysName: Linux<br />
NodeName: XXXX.test.org<br />
Release: 2.6.11-rc5<br />
Version: #12 Sun Feb 27 01:07:29 CET 2005<br />
Machine: i686<br />
DomainName: <br />
nr_threads: 16<br />
nr_running: 0<br />
nr_unintr: 0<br />
nr_onhold: 0<br />
load_updates: 14585<br />
loadavg: 0.00 0.00 0.00<br />
total_forks: 272<br />
<br />
=== limit ===<br />
Limit columns are: current (1), max observed (2), limit (3) and number of hits (4) <br />
<br />
Limit rows are: processes, virtual memory, locked memory, resident set size, anonymous memory, number of files, filedescriptors, locks, sockets, message queues, and shared memory<br />
<br />
/proc/virtual/<id>/limit <br />
PROC: 16 17 -1 0<br />
VM: 14440 15331 -1 0<br />
VML: 0 0 -1 0<br />
RSS: 5478 5847 -1 0<br />
ANON: 1516 1516 -1 0<br />
FILES: 140 155 -1 0<br />
OFD: 122 122 -1 0<br />
LOCKS: 1 3 -1 0<br />
SOCK: 9 9 -1 0<br />
MSGQ: 0 0 -1 0<br />
SHM: 0 0 -1 0<br />
<br />
== Debugging Control ==<br />
This complete directory seems not to be present by default. Possibly there is a compile- or a runtime-switch to enable debugging.<br />
<br />
/proc/sys/vserver<br />
.../debug_switch<br />
.../debug_xid<br />
.../debug_cvirt<br />
.../debug_limit<br />
.../debug_dlim<br />
.../debug_nid<br />
.../debug_net<br />
/proc/sys/vserver/debug_switch<br />
/proc/sys/vserver/debug_xid<br />
/proc/sys/vserver/debug_cvirt<br />
/proc/sys/vserver/debug_limit<br />
/proc/sys/vserver/debug_dlim<br />
/proc/sys/vserver/debug_nid<br />
/proc/sys/vserver/debug_net<br />
<br />
If the directory exist you should be able to create these files by issuing commands like:<br />
<br />
echo 255 >/proc/sys/vserver/debug_switch<br />
<br />
The bigger problem is to find out which values are useful, see [[Debugging]] for details.<br />
<br />
----<br />
''Please note: some samples are simply copied from the old wiki at http://oldwiki.linux-vserver.org/HowTo+Read+ProcFS, some other are captured from an Athlon AMD X2 system. They do not necessarily fit together.''</div>UdoBurghardt