-----Original Message----- From: development-bounces@drupal.org [mailto:development-bounces@drupal.org] On Behalf Of Scott McLewin Sent: Friday, June 02, 2006 11:50 AM
Second, I've made the same mistake several times across the Drupal based sites I manage. I've typically forgotten to modify cron-lynx.sh to point to my site and not www.example.com, and I forget to make the change until I notice that cron-driven content is a week or three out of date. I've since moved cron-lynx.sh out of the Drupal tree - this sort of admin warning that cron is not running would have helped me catch what is a slightly embarrassing mistake. Hopefully it's not just me making it. :)
Scott
Just a note. My sites can't use *nix cron. When considering automation consider that many Drupal sites do not run on *nix and some run on *nix with restrictions to the local cron.