Posted by DanielTheViking on August 12, 2009 at 1:04pm
Jump to:
| Project: | SuperCron |
| Version: | 6.x-1.x-dev |
| Component: | Documentation |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | reviewed & tested by the community |
Issue Summary
Should the existing cron.php file be removed if using supercron.php? Or does this module make use of the cron.php file?
What happens if cron.php is called when supercron is active?
If cron.php should be left:
- when using the IP-limitation feature, does it also limit direct calls to cron.php, or only to supercron.php?
This should be made clear in the readme.txt file, I think.
Comments
#1
Good points; cron.php can be left there but execution goes through the usual cron execution path. We use the same semaphore and timers so when they are used there will be mutual exclusion, but when they are not there will be conflict. I'll update the readme to indicate that cron.php should be removed to get the most stable environment.
#2
So, 100 words to say "remove cron.php" then. I'd actually suggest renaming it, which is I think more standard practise?
#3
@NikLP Or for optimal security move it to a non-served directory on the server. See also: http://nadeausoftware.com/articles/2009/06/drupal_and_apache_web_site_se...
#4
"So, 100 words to say "remove cron.php" then." hahahahahahaha I was also wondering the same thing. I have deleted my original cron.php (since I can get it anytime from Drupal.org)