diff options
author | Eric Wong <e@80x24.org> | 2019-03-11 23:53:02 +0000 |
---|---|---|
committer | Eric Wong <e@80x24.org> | 2019-04-04 09:13:58 +0000 |
commit | 89be7a1b89a60446fc0a385c5c1cfaeec2f92c88 (patch) | |
tree | 529a58f8cf4a2c3e119e71a494bae38e1646c8f4 /Documentation/public-inbox-config.pod | |
parent | 411dc580077c5240e9cfd4808c06623345435b69 (diff) | |
download | public-inbox-89be7a1b89a60446fc0a385c5c1cfaeec2f92c88.tar.gz |
This allows users to configure RLIMIT_{CORE,CPU,DATA} using our "limiter" config directive when spawning external processes.
Diffstat (limited to 'Documentation/public-inbox-config.pod')
-rw-r--r-- | Documentation/public-inbox-config.pod | 17 |
1 files changed, 17 insertions, 0 deletions
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<RLIMIT_*> keys may be set to enforce resource limits for +a particular limiter. + =over 8 =item publicinboxlimiter.<name>.max The maximum number of parallel processes for the given limiter. +=item publicinboxlimiter.<name>.rlimitCore + +=item publicinboxlimiter.<name>.rlimitCPU + +=item publicinboxlimiter.<name>.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<setrlimit(2)> for more info on the behavior of RLIMIT_CORE, +RLIMIT_CPU, and RLIMIT_DATA for you operating system. + =back =head3 EXAMPLE WITH NAMED LIMITERS |