[vserver] Bad (=zero) memory information in /proc/virtual/$ID/limit

From: Roman Vesely <roman_at_liten.cz>
Date: Sat 23 Jun 2012 - 20:39:18 BST
Message-ID: <20120623213918.214c0f40@ausus>

Hello,

After upgrade to 3.2 kernel all memory data in /proc/virtual/$ID/limit
is zero. Others are ok.

Limit current min/max soft/hard hits
PROC: 70 0/ 120 -1/ -1 0
VM: 0 0/ 0 -1/ -1 0
VML: 0 0/ 0 -1/ -1 0
RSS: 0 0/ 0 -1/ -1 0
ANON: 0 0/ 0 -1/ -1 0
RMAP: 0 0/ 0 -1/ -1 0
FILES: 1390 0/ 2025 -1/ -1 0
OFD: 1244 0/ 1467 -1/ -1 0
LOCKS: 8 0/ 32 -1/ -1 0
SOCK: 531 0/ 662 -1/ -1 0
MSGQ: 0 0/ 0 -1/ -1 0
SHM: 0 0/ 0 -1/ -1 0
SEMA: 0 0/ 0 -1/ -1 0
SEMS: 0 0/ 0 -1/ -1 0
DENT: 26029921 0/26029921 -1/ -1 0

Kernel is: 3.2.20-vs2.3.2.10-beng

It's bug or feature?
If feature, can get memory information elsewhere?

Thanks,

Roman
Received on Sat Jun 23 20:39:33 2012

[Next/Previous Months] [Main vserver Project Homepage] [Howto Subscribe/Unsubscribe] [Paul Sladen's vserver stuff]
Generated on Sat 23 Jun 2012 - 20:39:34 BST by hypermail 2.1.8