php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #23628 max_execution_time documentation wrong?
Submitted: 2003-05-14 07:37 UTC Modified: 2003-05-14 09:42 UTC
From: pekka at studio-on-the dot net Assigned:
Status: Not a bug Package: PHP options/info functions
PHP Version: 4.3.2RC2 OS:
Private report: No CVE-ID: None
View Developer Edit
 [2003-05-14 07:37 UTC] pekka at studio-on-the dot net 
ini_set (max_execution_time,"3600");

does not work in safe mode. Is documentation wrong?

I must strongly disagree if you have made changing maximum execution time harder or impossible to virtual servers clients. I have tried hard writing apps with full compability with safe mode because that is what most virtual server providers offer (and they of course refuse to change php.ini for clients' needs). Try doing e.g. PhpMyAdmin dump in 30 seconds... and that app is bundled with most servers in the world.

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2003-05-14 07:55 UTC] derick@php.net 
Sorry, but your problem does not imply a bug in PHP itself.  For a
list of more appropriate places to ask for help using PHP, please
visit http://www.php.net/support.php as this bug system is not the
appropriate forum for asking support questions. 

Thank you for your interest in PHP.

http://ch.php.net/manual/en/ref.info.php#ini.max-execution-time
has a link to: http://ch.php.net/manual/en/function.set-time-limit.php
which explains:

set_time_limit() has no effect when PHP is running in safe mode. There is no workaround other than turning off safe mode or changing the time limit in the php.ini.
 [2003-05-14 09:42 UTC] philip@php.net 
Also this has been added to the list of things affected by safe_mode and will show up during the next manual build.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Sat Dec 21 16:01:28 2024 UTC