Forums / Install & configuration / Patch for systems without phpcli

"Please Note:

At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

Patch for systems without phpcli

Previous topic

Install & configuration

Next topic

Author	Message
Rob Rob	Monday 20 June 2005 3:15:33 am On my shared account I don't have access with shell oder root right. This causes that the runcronjob was not running. So I looked up the forum to find a simple solution for me. I found this and tested it. http://www.ez.no/community/bugs/patch_for_systems_without_phpcli I works fine after I called my runcronjobs.php in the browser like http://www.mysite.com/myez/runcronjobs.php So my question is, what problems can cause this? I expect problems if the script is called very often and the server suffers, any other problems that I have to expect? Something simple to heal this disadvantage? Thanks for comments rob
Björn X	Monday 20 June 2005 3:53:41 am Basicly your main concern should be timeouts. When you run the runcronjobs from the web you will get a timeout at a certain point. This means you might break your db. So if you are in a need of running crons, I would recommend switching the host.

Author

Message

Rob Rob

Monday 20 June 2005 3:15:33 am

On my shared account I don't have access with shell oder root right. This causes that the runcronjob was not running.

So I looked up the forum to find a simple solution for me. I found this and tested it.

http://www.ez.no/community/bugs/patch_for_systems_without_phpcli

I works fine after I called my runcronjobs.php in the browser like

http://www.mysite.com/myez/runcronjobs.php

So my question is, what problems can cause this? I expect problems if the script is called very often and the server suffers, any other problems that I have to expect?
Something simple to heal this disadvantage?

Thanks for comments

rob

Björn X

Monday 20 June 2005 3:53:41 am

Basicly your main concern should be timeouts.

When you run the runcronjobs from the web you will get a timeout at a certain point.

This means you might break your db.

So if you are in a need of running crons, I would recommend switching the host.