Hello,
Here is my latest find
~ # date
Sun Nov 25 22:22:32 CET 2012
j%%%e 21389 6.6 0.0 29456 6480 ? RN Nov24 175:11 | \_ lsphptografhjo.%%%.se/templates/atomic/conf.php
I could not believe when I run ps axufw!
How it is possible? I use lsphp via lsapi v6, with
LSAPI_MAX_REQUESTS=15000
LSAPI_CHILDREN=100
PHP_INI_SCAN_DIR=/usr/local/lsws/lsphp52/etc/php.d
Instances 1. Means php is managed by lsphp but web server, yes?
LSAPI_MAX_IDLE is not set.
Web server have
Connection Timeout (secs) 320
And it is said in Documentation
LSAPI_MAX_IDLE (default value: 300 seconds)
In Self Managed Mode, LSAPI_MAX_IDLE controls how long a idle child process will wait for a new request before it exits. This option help releasing system resources taken by idle processes.
But the process I found is running at least a day and a half according to ps.
Why it gets out of the control? How to avoid it?
Here is my latest find
~ # date
Sun Nov 25 22:22:32 CET 2012
j%%%e 21389 6.6 0.0 29456 6480 ? RN Nov24 175:11 | \_ lsphptografhjo.%%%.se/templates/atomic/conf.php
I could not believe when I run ps axufw!
How it is possible? I use lsphp via lsapi v6, with
LSAPI_MAX_REQUESTS=15000
LSAPI_CHILDREN=100
PHP_INI_SCAN_DIR=/usr/local/lsws/lsphp52/etc/php.d
Instances 1. Means php is managed by lsphp but web server, yes?
LSAPI_MAX_IDLE is not set.
Web server have
Connection Timeout (secs) 320
And it is said in Documentation
LSAPI_MAX_IDLE (default value: 300 seconds)
In Self Managed Mode, LSAPI_MAX_IDLE controls how long a idle child process will wait for a new request before it exits. This option help releasing system resources taken by idle processes.
But the process I found is running at least a day and a half according to ps.
Why it gets out of the control? How to avoid it?
Last edited: