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. |
scripts/task_server.pl | ||
---|---|---|
25 | 25 |
use SL::DBUpgrade2; |
26 | 26 |
use SL::DB::AuthClient; |
27 | 27 |
use SL::DB::BackgroundJob; |
28 |
use SL::Dispatcher; |
|
28 | 29 |
use SL::BackgroundJob::ALL; |
29 | 30 |
use SL::Form; |
30 | 31 |
use SL::Helper::DateTime; |
... | ... | |
331 | 332 |
|
332 | 333 |
clean_before_sleeping(); |
333 | 334 |
|
335 |
if (SL::Dispatcher::_memory_usage_is_too_high()) { |
|
336 |
return; |
|
337 |
} |
|
338 |
|
|
334 | 339 |
my $seconds = 60 - (localtime)[0]; |
335 | 340 |
if (!eval { |
336 | 341 |
$SIG{'ALRM'} = sub { |
Auch abrufbar als: Unified diff
task_server.pl: Speicherlimit beachten
(cherry picked from commit 7fcf2ca9960d160419aa89824cb4fb3a25188ad9)