summaryrefslogtreecommitdiff
path: root/linux/Documentation/namespaces/resource-control.txt
diff options
context:
space:
mode:
authorMichael J. Chudobiak <mjc@avtechpulse.com>2016-04-25 10:00:44 -0400
committerMichael J. Chudobiak <mjc@avtechpulse.com>2016-04-25 10:00:44 -0400
commita1df417e74aa6dae7352dc8cbb0ad471af5b7c69 (patch)
treec34b2311e37ea31db153c90cb8f4570374d05e78 /linux/Documentation/namespaces/resource-control.txt
initial Olimex linux tree from Daniel, originally Feb 3, 2016
Diffstat (limited to 'linux/Documentation/namespaces/resource-control.txt')
-rw-r--r--linux/Documentation/namespaces/resource-control.txt14
1 files changed, 14 insertions, 0 deletions
diff --git a/linux/Documentation/namespaces/resource-control.txt b/linux/Documentation/namespaces/resource-control.txt
new file mode 100644
index 00000000..abc13c39
--- /dev/null
+++ b/linux/Documentation/namespaces/resource-control.txt
@@ -0,0 +1,14 @@
+There are a lot of kinds of objects in the kernel that don't have
+individual limits or that have limits that are ineffective when a set
+of processes is allowed to switch user ids. With user namespaces
+enabled in a kernel for people who don't trust their users or their
+users programs to play nice this problems becomes more acute.
+
+Therefore it is recommended that memory control groups be enabled in
+kernels that enable user namespaces, and it is further recommended
+that userspace configure memory control groups to limit how much
+memory user's they don't trust to play nice can use.
+
+Memory control groups can be configured by installing the libcgroup
+package present on most distros editing /etc/cgrules.conf,
+/etc/cgconfig.conf and setting up libpam-cgroup.