Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
By splarky on
I am not having much luck with my crontab. Does anything look obviously wrong that I've done:
- the crontab file:
00 * * * * /htdocs/www/drupal/scripts/cron-lynx
- the cron-lynx.sh file (this file is chmod 700):
#!/bin/sh
/usr/bin/lynx -source http://www.biptron.com/drupal/cron.php > /dev/null 2>&1
- the cron.php file:
// $Id: cron.php,v 1.15 2001/11/01 11:00:46 dries Exp $
include_once "includes/common.inc";
/*
** If not in 'safe mode', increase the maximum execution time:
*/
if (!get_cfg_var("safe_mode")) {
set_time_limit(180);
}
/*
** Iterate through the modules calling their cron handlers (if any):
*/
foreach (module_list() as $module) {
module_invoke($module, "cron");
}
Thanks,
--Art
Comments
the crontab entry obvisiously
the crontab entry obvisiously should be
00 * * * * /htdocs/www/drupal/scripts/cron-lynx<em>.sh</em>
note the
.sh
at the end. this has changed with the 4.0 release but not yet propagated to the handbook.didn't work
Thanks for your help. I made the change and it didn't work unfortunately. The main thing I'm gauging crontab success with is hourly updates to my newsfeeds (BBC & the Guardian) which are not updating.
I'm having this problem too :-( Pls help....
My cron entry looks like this :
# Drupal hourly cron call for news feed update
00 * * * * /export/home/public_html/drupal/scripts/cron-lynx.sh > /dev/null
My cron log shows this for every hour :
CMD: /export/home/public_html/drupal/scripts/cron-lynx.sh > /dev/null
root 3602 c Tue Oct 1 19:00:00 2002
root 3602 c Tue Oct 1 19:00:01 2002
CMD: /export/home/public_html/drupal/scripts/cron-lynx.sh > /dev/null
root 3724 c Tue Oct 1 20:00:00 2002
root 3724 c Tue Oct 1 20:00:00 2002
I'm assuming this means it worked ok? i.e. no errors or warnings. Can anyone help me get this going??
TIA
C.W.
P.S. I've become a drupal junky in only a few days - a very nice piece of work
script
Sometimes, depending on your terminal default, you have to stick a TERM=vt100 for lynx to work correctly.
Try adding it BEFORE the lynx line...