By lameei on

When i run cron manually i got this error or message what does it mean?

warning: set_time_limit() has been disabled for security reasons in /home/mostafal/public_html/includes/common.inc on line 2501

⋅ Categories: Drupal 6.x

Comments

gpk’s picture

gpk commented

Drupal tries to set/increase the PHP time limit here http://cvs.drupal.org/viewvc.py/drupal/drupal/includes/common.inc?annota... so that the cron run has more chance of finishing successfully. It only tries to do this if PHP's "safe mode" is not enabled. However, other things can prevent set_time_limit() from working. This is probably the situation in your case.

If you run phpinfo() on your server, near the top under configuration - PHP core, can you see set_time_limit listed under "disable_functions" directive?

It would also be nice if http://api.drupal.org/api/function/drupal_cron_run/6 only tried to set the time limit if it was sure that the current value was lower ..!

gpk
----
www.alexoria.co.uk

gpk
----
www.alexoria.co.uk

lameei’s picture

lameei commented

set_time_limit listed under "disable_functions". do I really need to enable it? if yes how? will enabling this cause a security issue?

gpk’s picture

gpk commented

If your host has disabled it then you won't be able to enable it (unless you maybe ask very nicely ;) ). If you can live with the warnings then I'd just do that. Chances are that the server default PHP processing time limit (usually 30s or 60s) will be enough anyway. A (minor) bug/issue could be opened against Drupal project to get rid of the warnings though. There are a couple of other places in core where the same thing can happen ... here's a similar issue http://drupal.org/node/174617.

gpk
----
www.alexoria.co.uk

gpk
----
www.alexoria.co.uk

lameei’s picture

lameei commented

Thanks for your time. I think I can live with the warning and it seems that everything is working nicely so i will let it go...