Move Drupal cron entry to /etc/cron.d/drupal

[Sean Bannister]

Currently the Drupal cron entry to run cron.php is located in "crontab -e". A better option would be to move it to /etc/cron.d/drupal

This seems to be a best practice but it also has two obvious benefits, /etc/cron.d/drupal becomes a central location for any Drupal related cron entries such as multiple Drupal sites requiring cron.php to be run. And it also allows us to easily symlink /etc/cron.d/drupal to an EBS volume for persistent storage.

[Sean Bannister (seanbannister)]

Just wanted to emphasis why this is needed, we can't symlink the "crontab -e" crontab to an EBS volume.

[Josh Koenig (joshkoenig)]

This makes sense to me. We're making a list of changes for the upcoming 0.8
release that's aimed at more stability and friendliness to other non-amazon
providers. This is a good move across the board.

On Sat, Nov 7, 2009 at 10:36 PM, Sean Bannister <email address hidden>wrote:

> Just wanted to emphasis why this is needed, we can't symlink the
> "crontab -e" crontab to an EBS volume.
>
> --
> Move Drupal cron entry to /etc/cron.d/drupal
> https://bugs.launchpad.net/bugs/478116
> You received this bug notification because you are the registrant for
> PANTHEON Mercury.
>
> Status in Open-source system configuration for high-performance Drupal: New
>
> Bug description:
> Currently the Drupal cron entry to run cron.php is located in "crontab -e".
> A better option would be to move it to /etc/cron.d/drupal
>
> This seems to be a best practice but it also has two obvious benefits,
> /etc/cron.d/drupal becomes a central location for any Drupal related cron
> entries such as multiple Drupal sites requiring cron.php to be run. And it
> also allows us to easily symlink /etc/cron.d/drupal to an EBS volume for
> persistent storage.
>

--
--------------------
Josh Koenig, Partner & CTO
http://www.chapterthree.com