As if the litany of Fortune 500 customers we’ve been talking to lately that are starting to use Drupal for high profile stuff isn’t enough, I discovered tonight that Network World actually uses Drupal to manage the content and community platform (essentially, their “product”).

Have a look at the article here.

So, after examining the problem, here is a solution to the Drupal cron multisite problem:

HTTP_HOST=”www.foo.com” php -q /path/to/cron.php

Turns out you can pass the host (which is the expected data. Solved. Next problem.

What do you do on a site with Drupal cron taking longer than an hour to execute, but where you need to keep the watchdog and access tables from consuming you (think VERY high traffic environments)?

The answer my friend, is to stop calling the cron directly, and start calling a shell script that checks for execution of the cron as a process on the machine your on before calling the cron again. If you don’t do this, you will pay as your cron will stack up processes and crash your machine, and you will be blamed for not ready this post. ;-)  read more »