Revision bc2b5fe6
Von Sven Schöling vor mehr als 5 Jahren hinzugefügt
| config/kivitendo.conf.default | ||
|---|---|---|
| 80 | 80 |
# processes). If either limit is reached at the end of the request |
| 81 | 81 |
# then the kivitendo process will exit. |
| 82 | 82 |
# |
| 83 |
# This only makes sense when running under FCGI. The FCGI manager will |
|
| 84 |
# then automatically start a new process. |
|
| 83 |
# This only applies for processes under FCGI and the task manager. |
|
| 84 |
# For CGI configurations the process will be terminated after each request |
|
| 85 |
# regardless of this setting. |
|
| 86 |
# |
|
| 87 |
# Note: this will only terminate processes with too high memory consumption. It |
|
| 88 |
# is assumed that an external managing service will start new instances. For |
|
| 89 |
# FCGI this will usually be apache or the wrapper scripts for nginx, for the |
|
| 90 |
# task server this will have to be the system manager. |
|
| 85 | 91 |
# |
| 86 | 92 |
# Numbers can be postfixed with KB, MB, GB. If no number is given or |
| 87 | 93 |
# the number is 0 then no checking will be performed. |
Auch abrufbar als: Unified diff
task_server.pl: Speicherlimit beachten
(cherry picked from commit 7fcf2ca9960d160419aa89824cb4fb3a25188ad9)