From 89be7a1b89a60446fc0a385c5c1cfaeec2f92c88 Mon Sep 17 00:00:00 2001 From: Eric Wong Date: Mon, 11 Mar 2019 23:53:02 +0000 Subject: qspawn: wire up RLIMIT_* handling to limiters This allows users to configure RLIMIT_{CORE,CPU,DATA} using our "limiter" config directive when spawning external processes. --- Documentation/public-inbox-config.pod | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) (limited to 'Documentation') diff --git a/Documentation/public-inbox-config.pod b/Documentation/public-inbox-config.pod index 9647e4a4..dae69987 100644 --- a/Documentation/public-inbox-config.pod +++ b/Documentation/public-inbox-config.pod @@ -228,12 +228,29 @@ large inboxes, it makes sense to put large inboxes on a named limiter with a low max value; while smaller inboxes can use the default limiter. +C keys may be set to enforce resource limits for +a particular limiter. + =over 8 =item publicinboxlimiter..max The maximum number of parallel processes for the given limiter. +=item publicinboxlimiter..rlimitCore + +=item publicinboxlimiter..rlimitCPU + +=item publicinboxlimiter..rlimitData + +The maximum core size, CPU time, or data size processes run with the +given limiter will use. This may be comma-separated to distinguish +soft and hard limits. The word "INFINITY" is accepted as the +RLIM_INFINITY constant (if supported by your OS). + +See L for more info on the behavior of RLIMIT_CORE, +RLIMIT_CPU, and RLIMIT_DATA for you operating system. + =back =head3 EXAMPLE WITH NAMED LIMITERS -- cgit v1.2.3-24-ge0c7