From 93f9e90d72da6f71e61b4812b94bb4065548cfa5 Mon Sep 17 00:00:00 2001 From: Wolfgang Bumiller Date: Fri, 4 Nov 2016 12:03:28 +0100 Subject: [PATCH] doc: add lxc.limit to lxc.container.conf Signed-off-by: Wolfgang Bumiller --- doc/lxc.container.conf.sgml.in | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) diff --git a/doc/lxc.container.conf.sgml.in b/doc/lxc.container.conf.sgml.in index fcccd8ba9..43f31397b 100644 --- a/doc/lxc.container.conf.sgml.in +++ b/doc/lxc.container.conf.sgml.in @@ -1183,6 +1183,40 @@ proc proc proc nodev,noexec,nosuid 0 0 + + Resource limits + + The soft and hard resource limits for the container can be changed. + Unprivileged containers can only lower them. Resources which are not + explicitly specified will be inherited. + + + + + + + + + Specify the resource limit to be set. A limit is specified as two + colon separated values which are either numeric or the word + 'unlimited'. A single value can be used as a shortcut to set both + soft and hard limit to the same value. The permitted names the + "RLIMIT_" resource names in lowercase without the "RLIMIT_" + prefix, eg. RLIMIT_NOFILE should be specified as "nofile". See + + setrlimit + 2 + . + If used with no value, lxc will clear the resource limit + specified up to this point. A resource with no explicitly + configured limitation will be inherited from the process starting + up the container. + + + + + + Apparmor profile