Scoop, like nearly any other weblog, needs to do some things at a
set interval. This is where cron comes in. Scoop's cron system is
mainly web-based, only requiring one actual crontab job, and that
doesn't even have to be on the same server as Scoop. In order to use
Scoop's cron, you'll need to have the cron daemon (or some other scheduler)
configured correctly on a system that will always be running (or at
least, always be running when it needs to be :). For more on setting
up cron to run Scoop's cron, see the Notes section (3.14.3).
3.14.1 Usage
Like all of Scoop's admin tools, you access the Cron admin tool using
the ``Cron'' link under ``Admin Tools''. Generally, you must
be a Superuser to access this (any lesser group probably has no need
to access it). When you do, you'll see a table at the top, which lists
all of the possible cron jobs. At the far left is a checkbox so that
you can perform several actions at once, followed by the name of the
cron job, and the internal function it relates to (you can't change
this without manually editing the DB because, well, there's no need
to). After that is a box setting how often to run the job, the time
it was last run, and if it's enabled or not.
Out of these, the ``Run Every'' column is probably the only one
that needs some explaining. Basically, it defines how often the job
should be run, in units of time between them. The format is ``