Proc/user beancounters - Revision history

Nathanhaigh: /* Reading */ fixed a typo

2011-08-15T23:28:21Z

‎Reading: fixed a typo

Nathanhaigh: /* Units */ Link directly to the main article for ease of maintenance

2011-08-15T23:24:45Z

‎Units: Link directly to the main article for ease of maintenance

Kir: MAX_ULONG -> LONG_MAX

2011-01-25T13:49:58Z

MAX_ULONG -> LONG_MAX

Kir: /* Reading */ note the new interface

2010-03-09T10:58:53Z

‎Reading: note the new interface

213.86.197.188: /* Reading */

2010-03-08T11:14:12Z

‎Reading

Kir: try to add slash to page name

2008-04-08T11:17:09Z

try to add slash to page name

Botinki Kira: Robot: Automated text replacement (-VE +container)

2008-03-11T11:12:03Z

Robot: Automated text replacement (-VE +container)

Botinki Kira: Robot: Automated text replacement (-Virtual Environment +container)

2008-03-11T10:39:29Z

Robot: Automated text replacement (-Virtual Environment +container)

Botinki Kira: Robot: Automated text replacement (-VEs +containers)

2008-03-11T09:48:18Z

Robot: Automated text replacement (-VEs +containers)

Botinki Kira: Robot: Automated text replacement (-VEID +CTID)

2008-03-11T09:43:16Z

Robot: Automated text replacement (-VEID +CTID)

@@ Line 70: / Line 70: @@
 Or with headers, though slightly harder to remember:
-   <nowiki>sed -nr "1,2p;/${CTID}:/,+23p' /proc/user_beancounters</nowiki>
+   <nowiki>sed -nr "1,2p;/${CTID}:/,+23p" /proc/user_beancounters</nowiki>
 Here <code>${CTID}</code> is the ID of the container you are interested in.

@@ Line 51: / Line 51: @@
 the <code>limit</code> for the parameter.
-== Units of measurement ==
+== Units ==
-As also discussed in [[UBC parameter units]], all values related to parameters with
+{{Main|UBC parameter units}}
 == Settings ==

@@ Line 61: / Line 61: @@
 General notes about parameters and their barrier and limit settings
 are provided in [[UBC parameters]]. Parameters not having limit setting have
-[[MAX_ULONG]] in the corresponding field.
+[[LONG_MAX]] in the corresponding field.
 == Reading ==

← Older revision		Revision as of 10:58, 9 March 2010
Line 64:		Line 64:

	== Reading ==		== Reading ==
		+
		+	{{Note\|It's easier to use [[BC proc entries\|the new <code>/proc/bc</code> interface]], i.e. <code>cat /proc/bc/$CTID/resources</code>.}}

	If you want to print UBC values for a specific container, the following construct can be helpful		If you want to print UBC values for a specific container, the following construct can be helpful

@@ Line 67: / Line 67: @@
 If you want to print UBC values for a specific container, the following construct can be helpful
-   <nowiki>egrep -A23 '^[[:space:]]+${CTID}:' /proc/user_beancounters</nowiki>
+   <nowiki>egrep -A23 "${CTID}:" /proc/user_beancounters</nowiki>
 Here <code>${CTID}</code> is the ID of the container you are interested in.

@@ Line 1: / Line 1: @@
 {{UBC toc}}
-{{DISPLAYTITLE:proc/user_beancounters}}
+{{DISPLAYTITLE:/proc/user_beancounters}}
 The proc filesystem entry showing resource control information is <code>/proc/user_beancounters</code> file. An example content of <code>/proc/user_beancounters</code> is shown below.

@@ Line 40: / Line 40: @@
 The field '''<code>uid</code>''' is a numeric identifier of the container<ref>The name “uid” is related to the fact that OpenVZ Resource Management can be used without virtualization and containers.</ref>.
-For accountable parameters, the field '''<code>held</code>''' shows the current counter for the container (resource “usage”), and the field '''<code>maxheld</code>''' shows the counter's maximum for the last accounting period. The accounting period is usually the lifetime of the container<ref>The lifetime of a container is the period from the start of the VE till the time all processes in the VE exited and all resources used by these processes are freed. Usually, the lifetime is just the time between the start and the stop of the container.</ref>.
+For accountable parameters, the field '''<code>held</code>''' shows the current counter for the container (resource “usage”), and the field '''<code>maxheld</code>''' shows the counter's maximum for the last accounting period. The accounting period is usually the lifetime of the container<ref>The lifetime of a container is the period from the start of the container till the time all processes in the container exited and all resources used by these processes are freed. Usually, the lifetime is just the time between the start and the stop of the container.</ref>.
 The field '''<code>failcnt</code>''' shows the number of refused “resource allocations” for the whole lifetime of the process group.
@@ Line 65: / Line 65: @@
 == Reading ==
-If you want to print UBC values for a specific VE, the following construct can be helpful
+If you want to print UBC values for a specific container, the following construct can be helpful
    <nowiki>egrep -A23 '^[[:space:]]+${CTID}:' /proc/user_beancounters</nowiki>
-Here <code>${CTID}</code> is the ID of the VE you are interested in.
+Here <code>${CTID}</code> is the ID of the container you are interested in.
 In case you want to print UBC values for a few containers at once, set CTID to something like <code>(101|102|103)</code>.

@@ Line 38: / Line 38: @@
 == Fields ==
-The field '''<code>uid</code>''' is a numeric identifier of the Virtual Environment<ref>The name “uid” is related to the fact that OpenVZ Resource Management can be used without virtualization and Virtual Environments.</ref>.
+The field '''<code>uid</code>''' is a numeric identifier of the container<ref>The name “uid” is related to the fact that OpenVZ Resource Management can be used without virtualization and containers.</ref>.
-For accountable parameters, the field '''<code>held</code>''' shows the current counter for the Virtual Environment (resource “usage”), and the field '''<code>maxheld</code>''' shows the counter's maximum for the last accounting period. The accounting period is usually the lifetime of the Virtual Environment<ref>The lifetime of a Virtual Environment is the period from the start of the VE till the time all processes in the VE exited and all resources used by these processes are freed. Usually, the lifetime is just the time between the start and the stop of the Virtual Environment.</ref>.
+For accountable parameters, the field '''<code>held</code>''' shows the current counter for the container (resource “usage”), and the field '''<code>maxheld</code>''' shows the counter's maximum for the last accounting period. The accounting period is usually the lifetime of the container<ref>The lifetime of a container is the period from the start of the VE till the time all processes in the VE exited and all resources used by these processes are freed. Usually, the lifetime is just the time between the start and the stop of the container.</ref>.
 The field '''<code>failcnt</code>''' shows the number of refused “resource allocations” for the whole lifetime of the process group.

@@ Line 71: / Line 71: @@
 Here <code>${CTID}</code> is the ID of the VE you are interested in.
-In case you want to print UBC values for a few VEs at once, set CTID to something like <code>(101|102|103)</code>.
+In case you want to print UBC values for a few containers at once, set CTID to something like <code>(101|102|103)</code>.
 == Notes ==
 <references/>