hi,
see the note:
"The set_time_limit() function and the configuration directive max_execution_time only affect the execution time of the script itself. Any time spent on activity that happens outside the execution of the script such as system calls using system(), stream operations, database queries, etc. is not included when determining the maximum time that the script has been running. This is not true on Windows where the measured time is real."
which means that your script can took more than 30 seconds before the limit of max_execution_time kicks in.
request_terminate_timeout on the other hand doesn't care about what does your script doing, it will terminate the script after the set amount of time.
On Fri, Jan 4, 2013 at 4:09 PM, Amod Pandey <amodpandey@xxxxxxxxx> wrote:
Is this expected or anything wrong?If request_terminate_timeout is NOT set in the php-fpm then the script does not stop!! Even though the browser times out with 504. If I set request_terminate_timeout the php process timesout at the specified time. I was assuming the php script will timeout at 30 seconds.We are running php-fpm with nginx.Hi,I have configured max_execution_time = 30 in php.ini. There is no place it is altered.
--
Amod
Ferenc Kovács
@Tyr43l - http://tyrael.hu
- Follow-Ups:
- Re: max_execution_time - fpm setup with nginx
- From: Amod Pandey
- Re: max_execution_time - fpm setup with nginx
- References:
- max_execution_time - fpm setup with nginx
- From: Amod Pandey
- max_execution_time - fpm setup with nginx
- Prev by Date: max_execution_time - fpm setup with nginx
- Next by Date: Re: max_execution_time - fpm setup with nginx
- Previous by thread: max_execution_time - fpm setup with nginx
- Next by thread: Re: max_execution_time - fpm setup with nginx
- Index(es):