From 9b19cd2fab9e2588ce11b4a520e5ef54fa3cec5b Mon Sep 17 00:00:00 2001 From: Aleksa Sarai Date: Wed, 28 Oct 2015 19:07:48 +1100 Subject: [PATCH] config: linux: update description of PidsLimit Fix a misleading comment for how PidsLimit works when given a limit of 0. In the PIDs controller, a limit of 0 is identical to a limit of 1, since it is not possible to impose a limit on 0 processes. As such, it makes no sense to distinguish the two values, rather the value 0 (which is also the default value of an integer in Go) should instead indicate no limit (which is the default for all new PIDs controllers). Signed-off-by: Aleksa Sarai --- runtime_config_linux.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/runtime_config_linux.go b/runtime_config_linux.go index e796e4941..bcace7e1a 100644 --- a/runtime_config_linux.go +++ b/runtime_config_linux.go @@ -182,7 +182,7 @@ type CPU struct { // Pids for Linux cgroup 'pids' resource management (Linux 4.3) type Pids struct { - // Maximum number of PIDs. A value < 0 implies "no limit". + // Maximum number of PIDs. A value <= 0 indicates "no limit". Limit int64 `json:"limit"` }