FastCGI Maximum ActivityTimeout

Gengar003 — Mon, 24 Nov 2008 18:14:17 GMT

Hello... on my IIS7 server, I have php implemented via fastCGI.

(Windows Server 2008 build 6001, IIS7 version 7.0.6)

Some of my scripts I need to run for extended periods of time, up to several hours.

While PHP itself has no qualms about this, IIS7's FastCGI "ActivityTimeout" setting refuses to allow itself to be set to more than 3600 seconds (1 hour).

This is inadequate. Using the management console, I cannot set the value to more than 3600, and when I edit the .xml file directly and restart the server, the .xml file is changed to contain 3600, instead of the value I chose.

What can I do to allow a php script to run for more than 3600 seconds (FastCGI's maximum ActivityTimeout)?

A good deal of the script in question's time is spent sleep()ing - is it possible to have FastCGI not count that time toward the activity timeout? Or is there a way to send IIS7 some "activity" from a php script, and thus re-set the timer?

Are there any updates or workarounds that will solve this for me?

Thanks in advance

Search results matching tag 'maximum'

FastCGI Maximum ActivityTimeout