From 704ebb393772556140f1d9aba82d924035473ad8 Mon Sep 17 00:00:00 2001 From: Emilien Mantel Date: Wed, 27 May 2020 10:15:42 +0200 Subject: [PATCH] Manage pm.max_requests on PHP pool --- templates/etc/__php__/fpm/pool.d/pool.conf.j2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/templates/etc/__php__/fpm/pool.d/pool.conf.j2 b/templates/etc/__php__/fpm/pool.d/pool.conf.j2 index 77f7f0a..e6eef97 100644 --- a/templates/etc/__php__/fpm/pool.d/pool.conf.j2 +++ b/templates/etc/__php__/fpm/pool.d/pool.conf.j2 @@ -132,7 +132,7 @@ pm.process_idle_timeout = {{ item.pm_process_idle_timeout | default('10s') }}; ; This can be useful to work around memory leaks in 3rd party libraries. For ; endless request processing specify '0'. Equivalent to PHP_FCGI_MAX_REQUESTS. ; Default Value: 0 -;pm.max_requests = 500 +pm.max_requests = {{ item.pm.max_requests | default('0') }} ; The URI to view the FPM status page. If this value is not set, no URI will be ; recognized as a status page. It shows the following informations: