This shows you the differences between the selected revision and the current version of the page.
|
litespeed_wiki:php_run_without_timeout 2013/03/01 02:29 |
litespeed_wiki:php_run_without_timeout 2013/03/01 02:30 current |
| | | | |
| | For example, when a php application rebuilds mysql indexes, the process may run for a long time. In Apache/mod_php, the ignore_user_abort variable allows the user to trigger this process and then close the browser or navigate away from the page without killing the php/mysql process. | | For example, when a php application rebuilds mysql indexes, the process may run for a long time. In Apache/mod_php, the ignore_user_abort variable allows the user to trigger this process and then close the browser or navigate away from the page without killing the php/mysql process. |
| | + | |
| | | | |
| | | | |
| | max_execution_time=36000 | | max_execution_time=36000 |
| | | | |
| - | * LSAPI_MAX_PROCESS_TIME | + | * LSAPI_MAX_PROCESS_TIME (set this environment variable in lsphp5) |
| | | | |
| - | You can set this environment variable in lsphp5 | + | Admin CP => Configuration => Server(or Vhost) => External App => lsphp5 |
| - | (Admin CP => Configuration => Server(or Vhost) => External App => lsphp5) | + | |
| | | | |
| | In Self Managed Mode, LSAPI_MAX_PROCESS_TIME (default 300 seconds) controls the maximum processing time allowed when processing a request. If a child process cannot finish processing the request in the given time period, it will be killed by the parent process. This option can get rid of a dead or a runaway child process. | | In Self Managed Mode, LSAPI_MAX_PROCESS_TIME (default 300 seconds) controls the maximum processing time allowed when processing a request. If a child process cannot finish processing the request in the given time period, it will be killed by the parent process. This option can get rid of a dead or a runaway child process. |
